Box, Dropbox & Google Drive to OneDrive Migration — Managed Cloud Document Migration

IT Partner’s document migration service includes planning, source data discovery, OneDrive account preparation, pre-stage migration, final delta sync, user and permission mapping, issue identification and fixing, user notifications, post-migration verification, and a project closeout report. The service is managed by an assigned Project Manager and is designed for organizations moving documents from a source platform — Box, Dropbox, or Google Drive — into OneDrive for Business, SharePoint Online, or Microsoft Teams.

This service supports cloud-to-cloud document migration from Box, Dropbox, or Google Drive. The destination can be OneDrive for Business, SharePoint Online, or Microsoft Teams within Microsoft 365.

Yes. Although the service title references OneDrive for Business, the stated scope includes migration to OneDrive for Business, SharePoint Online, or Microsoft Teams.

IT Partner first migrates historical documents and folders during a pre-stage migration, because this reduces the amount of data that must be moved during final cutover. A final delta sync is then performed to capture changes made during the project.

A final delta sync captures last-minute changes made after the pre-stage migration and before completion. Users should avoid modifying documents during the final cutover window, because changes during that period can complicate synchronization and verification.

The stated service duration is 5 days. The exact timing may depend on source data discovery, user lists, permissions, issue resolution, and coordination during the final cutover window.

The service is priced at $7 per user plus a $1,500 tenant fee. If there is any uncertainty about which users count for your environment, confirm the user count and pricing basis with IT Partner before the project begins.

IT Partner requires Global Admin access to Microsoft 365 and admin access to the source platform, which may be Box, Dropbox, or Google Drive. These permissions are prerequisites because IT Partner must prepare destination accounts, discover source data, map users and permissions, and perform the migration.

The client must provide Global Admin access to Microsoft 365 and admin access to the source platform. Users should also avoid modifying documents during the final cutover window, because the service includes a final delta sync and verification after migration.

IT Partner handles the cloud document migration, including planning, pre-stage migration, final delta sync, user and permission mapping, issue identification and fixing, user notifications, post-migration verification, and project management. IT Partner also provides a project closeout report after completion.

Yes. User and permission mapping from the source platform to OneDrive or SharePoint is included, and preserving files, folders, and permissions is part of the stated success criteria.

The service’s stated success criteria include full fidelity, zero data loss, and preservation of every file, folder, and permission. IT Partner also performs post-migration verification and resolves identified issues related to naming limits, file size, and permissions.

IT Partner identifies and fixes errors related to naming limits, file size, and permissions. These issues are common in document migrations because different platforms can have different constraints for file names, paths, sizes, and access models.

Yes. User notifications during the migration process are included in the service, because coordination is needed for pre-stage migration, final cutover, delta sync, and verification.

The service description does not specify a formal downtime window, but users should avoid modifying documents during the final cutover window. The pre-stage migration approach is intended to move historical content first and then capture changes with a final delta sync, which helps reduce disruption.

After migration, IT Partner performs post-migration verification, resolves identified issues, and provides a project closeout report. Decommissioning of the source platform is not included and remains the client’s responsibility.

No. Decommissioning of the source platform — account closure, subscription cancellation, or deletion of data on the source side — is not included in this service. After post-migration verification and the closeout report, the client decides when and how to retire the source platform.

The stated scope includes post-migration verification, issue resolution for identified migration issues, and a project closeout report. A separate support duration, support channel, or SLA is not included, so any ongoing support should be confirmed with IT Partner separately.

Decommissioning of the source platform and project documentation beyond the closeout report are not included. Also excluded are restructuring of source content, information architecture design, cleanup and classification work, non-document workloads such as email or chats, custom scripting, end-user training, licensing costs, recovery of inaccessible source data, compliance configuration, and ongoing managed support. See the full exclusions list on this page.