Box to SharePoint Migration
Budget: $25 – $50 USD
We have an upcoming migration of 100 users from Box.com to SharePoint in July. The dates are still being determined but will be after the July 4th holiday weekend. The client has decided to contract Involv-Intranet Professional Services for much of the back-end work to build out SharePoint.
Here are some skills, experience, and requirements:
Managed Services Engineer
Datto RMM (formerly Centerstage)
TeamWork / OneNote for Project Management
Box Plug-ins like Edit, Sync, etc
SharePoint (OneDrive)
Involv-Intranet
Roles:
Project Manager
Sr. Migration Engineers
Migration Engineers
Technical Writer
O365 Instructor/Trainer
Personal Qualities:
Confidence in Reason when working with end-users.
Attention to Detail in all training, emails, and resources
Accountability for your tasks/domain during the project
Humility and suppressed ego/overconfidence
Team fixer who can jump in to help where we find gaps
Writing, updating, and delivering documentation
Desktop migrations are simple, but you'd be amazed how much our internal colleagues will flood the chat with questions already answered in our playbook/ramp-up videos or hang up users on the phone for an hour or longer because they don't know the process. It's easy to overthink when you know so much and entirely miss the point of something when thinking of the most complex ways in places where simple will suffice.
Thanks!
Here are some skills, experience, and requirements:
Managed Services Engineer
Datto RMM (formerly Centerstage)
TeamWork / OneNote for Project Management
Box Plug-ins like Edit, Sync, etc
SharePoint (OneDrive)
Involv-Intranet
Roles:
Project Manager
Sr. Migration Engineers
Migration Engineers
Technical Writer
O365 Instructor/Trainer
Personal Qualities:
Confidence in Reason when working with end-users.
Attention to Detail in all training, emails, and resources
Accountability for your tasks/domain during the project
Humility and suppressed ego/overconfidence
Team fixer who can jump in to help where we find gaps
Writing, updating, and delivering documentation
Desktop migrations are simple, but you'd be amazed how much our internal colleagues will flood the chat with questions already answered in our playbook/ramp-up videos or hang up users on the phone for an hour or longer because they don't know the process. It's easy to overthink when you know so much and entirely miss the point of something when thinking of the most complex ways in places where simple will suffice.
Thanks!