RSS

Stop and Resume a Migration Run at Any Time

A migration run can be stopped at any time and resumed later. WikiTraccs picks up where it left off, whether you stopped it deliberately or it crashed.

Every migration run follows the same pattern: WikiTraccs connects to Confluence, asks which content needs to be migrated, then checks SharePoint for what is already there. Whatever is missing gets created. This makes every run inherently resumable.

How WikiTraccs Handles Existing Content

When WikiTraccs finds a page that already exists in SharePoint, it does one of two things depending on your configuration:

  • Leave it alone (default): If the page already exists in SharePoint, WikiTraccs skips it and moves on to the next one. This is the fastest option for large migrations where most content has already been transferred.
  • Overwrite outdated pages: If enabled, WikiTraccs compares the Confluence page version with the version that was last transferred to SharePoint. If the Confluence page has been updated since, WikiTraccs overwrites the SharePoint page with the latest content.

The overwrite behavior is controlled by the Update outdated SharePoint pages setting. See Update Outdated Pages for details on how to enable it and what it does.

Stop and Resume

You can stop a migration run at any time by clicking the Stop run button in the WikiTraccs GUI. The current page transfer completes, then the application shuts down gracefully.

To resume, just start the migration again. WikiTraccs will check Confluence and SharePoint, determine what is still missing, and continue from there. Pages that were already migrated are either skipped or updated, depending on your settings.

This also covers unplanned interruptions. If the application crashes, your machine restarts, or the network drops — simply run the migration again. WikiTraccs picks up where it left off. No manual bookkeeping, no restart files, no risk of duplicating content.