IT Partner migrates files and documents from a local file server to SharePoint Online as-is, keeping the existing folder structure and synchronizing files that have changed since the migration process started. We install Microsoft's migration agent on the source Windows Server, set it up, oversee the migration, and fix errors as they arise. The destination SharePoint Online environment must already be fully set up and ready to receive files — SharePoint preparation is a separate service.
IT Partner will migrate your files and documents from the local file server to SharePoint Online while preserving the folder structure. The work centers on Microsoft's migration tooling: we install the Microsoft migration agent on your source Windows Server, configure it, oversee the migration runs, and fix errors as they arise. IT Partner will also make sure the sync process is running so changed files are being migrated continuously. The destination SharePoint Online environment must already be set up and ready for file migration — building it is covered by our separate SharePoint Online - Initial Planning and Setup service. After migration, IT Partner will provide a detailed report listing files that could not be migrated, such as files affected by access or permission issues or bad file names. Upon completion of the project, IT Partner will provide a project closeout report indicating final project status, including evidence of matching acceptance criteria, outstanding issues if any, and the final budget.
Confirm migration objectives, source file share locations, estimated data volume, SharePoint Online destination sites and document libraries, access requirements, communications approach, migration timing, change-freeze expectations, and acceptance criteria.
Install and configure the Microsoft migration agent on the source Windows Server, map source folders to the agreed SharePoint Online destinations, run the initial migration pass while preserving the folder structure, and enable ongoing synchronization for files that change after the initial copy begins.
Review migration results, compare source and destination counts where practical, validate representative folders and files in SharePoint Online, confirm users can access migrated content as expected, and identify files that require remediation because of naming, access, permission, path length, or other migration exceptions.
Coordinate the final migration window with the customer, confirm users have been instructed not to modify files during the project and cutover, run the final synchronization pass, capture remaining exceptions, and confirm the SharePoint Online destination is ready for user access.
Provide post-migration break-fix support, review unresolved migration exceptions with the customer, deliver the detailed migration exception report and project closeout report, and confirm completion against the stated success criteria.
IT Partner migrates files and documents from a local file server to SharePoint Online as-is, preserving the existing folder structure. We install the Microsoft migration agent on the source Windows Server, configure it, run and oversee the migration, fix arising errors, and provide reporting on migration status and exceptions.
“As-is” means IT Partner migrates the existing files and documents while keeping the current folder structure. Files are not reorganized, redesigned, or reclassified during the migration — restructuring or metadata enrichment is available separately through the SharePoint Online Migration with Metadata service.
The service includes a Document Migration Plan, inspection of files and folders, installation and configuration of the Microsoft migration agent on the source Windows Server, migration from the local file server to SharePoint Online, migration sync setup, oversight with error fixing, post-migration break-fix support, and a project closeout report. IT Partner also provides a detailed list of files that could not be migrated, such as files with access issues, permission issues, or bad file names.
Training of the customer team, mail server migration, desktop software settings, and extensive documentation beyond the project closeout report are not included. These items may require a separate or additional service if needed.
The listed service duration is 1 week. Larger or more complex file shares can take longer, so data volume and timing should be confirmed with IT Partner before the project starts.
The service is priced at a fixed $4,500 per server, quoted in writing before work begins — you pay after you approve delivery. Anything beyond the agreed scope — such as additional source servers or building the destination SharePoint Online environment — is quoted separately.
The customer must have a Microsoft 365 tenant with SharePoint Online licenses, a destination SharePoint Online environment that is fully set up and ready for file migration, admin access to SharePoint Online, and a file server connected to the Internet with local administrator access for the migration agent install. If the destination environment still needs to be built, that is covered by the separate SharePoint Online - Initial Planning and Setup service.
Yes, preserving the existing folder structure is part of the stated service scope. IT Partner migrates files and documents from the local file server to SharePoint Online while keeping the folder structure.
IT Partner keeps the sync process running so files changed after the initial copy are migrated continuously. Users should still be told not to modify documents around the final migration window, because changes made during the final cutover will not be included — the exact change-freeze approach is agreed with IT Partner during planning.
IT Partner provides a detailed report listing files that could not be migrated. Common reasons named in the service scope include access or permission issues, bad file names, or similar file-level problems.
No. The destination SharePoint Online environment must already be fully set up and ready for file migration before this service starts — sites, document libraries, and permissions in place. Building and designing that environment is covered by the separate SharePoint Online - Initial Planning and Setup service.
The stated scope confirms migration of files and documents while preserving folder structure, but it does not specify a permissions redesign or detailed access model redesign. Because access and permission issues may prevent some files from migrating, permission-related requirements should be reviewed with IT Partner before the project starts.