What is SharePoint incremental migration?

It is a subsequent migration pass that processes supported new or modified SharePoint content after an earlier migration while avoiding unnecessary reprocessing of content already migrated.

Do I need to use the same computer for incremental migration?

The current EdbMails FAQ states that repeated migration of a previously migrated SharePoint site should use the same computer for the incremental check to be effective.

Can incremental migration help with final cutover?

Yes. It can be used after the main migration to capture supported content that changed while the source remained active.

Does incremental migration mean nothing can ever be duplicated?

Incremental processing is designed to avoid unnecessary reprocessing of content already migrated when the documented conditions are maintained. Review logs after each pass to confirm results.

Do I need to use the same target for an incremental migration pass?

Yes. EdbMails performs the incremental check against the same target used for the earlier migration, so later passes should reconnect to the same target environment.

What happens if the source-to-target site mapping changes between passes?

Keep the source-to-target mapping consistent for the incremental check to work as documented, unless an intentional mapping change is part of the project. Review the logs after a mapping change to confirm the results.

Can I retry failed or skipped items using incremental migration?

Yes. You can re-run the migration after resolving failed or skipped items so the next pass processes the outstanding supported content without restarting the whole project.

How do I confirm that an incremental pass completed correctly?

Review the EdbMails migration logs after each pass for completed, skipped and failed items instead of assuming every required item was processed.

Does incremental SharePoint migration require Microsoft Entra app registration?

Yes. The documented SharePoint migration workflow uses separate Source and Target Microsoft Entra app registrations, and incremental passes reconnect using the same workflow.

Can incremental migration run multiple SharePoint sites in one pass?

Yes. EdbMails can process multiple SharePoint sites in parallel, and an incremental pass can cover the mapped sites included in the migration scope.

SharePoint Incremental Migration

Transfer SharePoint Changes After the Initial Migration

EdbMails supports incremental SharePoint migration to help transfer eligible changes after an initial migration pass. Run subsequent migrations to bring across new or updated supported content, reduce unnecessary repeat transfers, and review results before completing your planned transition.

How SharePoint Incremental Migration Works

SharePoint incremental migration allows administrators to run additional migration passes after the initial SharePoint migration so supported new or modified content can be transferred without unnecessarily processing the same previously migrated content again.

EdbMails supports incremental migration when migrating SharePoint to the same target from the same source computer or migration environment used for the earlier operation. The application keeps migration metadata locally and uses it during subsequent runs to identify previously processed content.

Why incremental migration is important

Large SharePoint migration projects are rarely completed in a single moment. Users may continue working in the source tenant while the first migration is running, which means files, folders or other supported SharePoint content can change before the final transition. Incremental migration provides a practical way to perform the main migration first and then capture supported changes in later passes.

How EdbMails SharePoint incremental migration works

Run the initial migration. Connect the source and target tenants, select the SharePoint sites, map the sites and complete the first migration pass.

Keep the migration environment consistent. Use the same source computer or migration environment for later incremental runs where required by the documented incremental check.

Retain the local migration metadata. EdbMails stores certain migration metadata locally in encrypted form; it does not need to store the entire SharePoint site data for the incremental check.

Run the next migration pass. Reconnect to the same source and target mapping and start migration again.

Process supported changes. The incremental check is used to avoid unnecessary reprocessing of content already migrated and to process supported new or changed data.

Review the logs. Check completed, skipped or failed items after the incremental run.

When to use incremental SharePoint migration

Long migration projects: Use multiple passes when a large number of sites cannot be moved in one window.

Active source environment: Capture supported changes created while users continue working in SharePoint.

Final cutover: Run a catch-up migration shortly before users are transitioned to the target.

Retry and completion: Re-run the migration after resolving failed or skipped items without restarting the entire project from scratch.

Phased migration: Move departments or site groups in controlled waves and keep later runs aligned with the same target.

Initial migration vs incremental migration

Initial migration	Incremental migration
Creates the first target copy of the selected supported SharePoint content.	Runs after an earlier migration to process supported new or modified content.
Usually processes the full approved migration scope.	Uses migration metadata to avoid unnecessary reprocessing of already migrated content.
Establishes the site mapping and baseline.	Depends on consistent source/target mapping and the documented incremental environment.
Often takes place earlier in the project.	Useful for catch-up runs and the final transition.

Important incremental migration requirements

Use the same target for the subsequent migration.

Preserve the EdbMails migration metadata used for incremental checking.

Where documented, run the repeated migration from the same source computer to maintain the incremental history.

Keep source-to-target site mapping consistent unless an intentional mapping change is part of the project.

Review logs after every pass instead of assuming the incremental run completed every required item.

Recommended final-cutover approach

Complete the main SharePoint migration in planned batches.

Review migration logs and resolve failed items.

Confirm the target site mapping with site owners.

Schedule the final transition window.

Run an incremental pass for supported content changed since the earlier migration.

Validate representative content in the target.

Only then complete the operational cutover according to the organization's migration plan.

Frequently Asked Questions

What is SharePoint incremental migration?
It is a subsequent migration pass that processes supported new or modified SharePoint content after an earlier migration while avoiding unnecessary reprocessing of content already migrated.
Does EdbMails store the complete SharePoint site locally for incremental migration?
No. The current FAQ states that EdbMails stores certain migration metadata locally in encrypted form rather than the entire SharePoint site data.
Do I need to use the same computer for incremental migration?
The current EdbMails FAQ states that repeated migration of a previously migrated SharePoint site should use the same computer for the incremental check to be effective.
Can incremental migration help with final cutover?
Yes. It can be used after the main migration to capture supported content that changed while the source remained active.
Does incremental migration mean nothing can ever be duplicated?
Incremental processing is designed to avoid unnecessary reprocessing of content already migrated when the documented conditions are maintained. Review logs after each pass to confirm results.
Do I need to use the same target for an incremental migration pass?
Yes. EdbMails performs the incremental check against the same target used for the earlier migration, so later passes should reconnect to the same target environment.

What happens if the source-to-target site mapping changes between passes?
Keep the source-to-target mapping consistent for the incremental check to work as documented, unless an intentional mapping change is part of the project. Review the logs after a mapping change to confirm the results.
Can I retry failed or skipped items using incremental migration?
Yes. You can re-run the migration after resolving failed or skipped items so the next pass processes the outstanding supported content without restarting the whole project.
How do I confirm that an incremental pass completed correctly?
Review the EdbMails migration logs after each pass for completed, skipped and failed items instead of assuming every required item was processed.
Does incremental SharePoint migration require Microsoft Entra app registration?
Yes. The documented SharePoint migration workflow uses separate Source and Target Microsoft Entra app registrations, and incremental passes reconnect using the same workflow.
Can incremental migration run multiple SharePoint sites in one pass?
Yes. EdbMails can process multiple SharePoint sites in parallel, and an incremental pass can cover the mapped sites included in the migration scope.