Scan Archive and Cold Storage
MigrationFox keeps your scans and migrations. To keep that sustainable, the per-file detail of a scan or migration that has been idle past its retention window is moved from the live database to cold storage. The summary stays where it was. The file list comes back with one click when you need it.
What stays in place
The migration's name, status, counts (files, data, errors), start and finish times, settings and error summary. That is enough to show it in your migration list and on its page as usual. Only the per-file detail (the list of scanned items and per-file results) moves to cold storage.
What you’ll see
An archived migration looks the same in your migration list. On its page you’ll see a small Archived badge next to the title. Hover it to see the date the file-level data was moved.
The summary is all still there: file count, data size, start and finish times, and any error summary. What isn’t shown right away is the per-file list on the Files tab.
On the Files tab of an archived migration you’ll see File details are archived, the date they were moved to cold storage, and a Restore file details button. Click it, wait a few seconds, and the page reloads with the full file list. The badge goes away.
Archiving happens automatically for every workspace. It runs once a day and handles up to 100 eligible migrations per run, so a large backlog is spread over several days.
Retention thresholds
How long a migration stays idle before its file detail is archived depends on how it ended. Only finished migrations are ever archived. Migrations that are running or paused are never touched.
| How it ended | Days idle before archive | Why |
|---|---|---|
| Canceled | 1 day | You stopped it. Rarely needed again. |
| Failed | 7 days | Usually looked at and retried within a week. |
| Scan complete | 14 days | A scan finished and no copy was run from it yet. Time to review the results. |
| Completed | 14 days | The migration finished. Time for checks, reruns or rollback. |
“Days idle” counts from the last time the migration's record changed, which is normally when it finished. Retrying or resuming it starts the clock again once it finishes again.
Running and paused migrations are never archived
Only canceled, failed, scan-complete and completed migrations can be archived. A migration that is scanning, transferring or paused is skipped, so you can leave one paused for weeks without it being archived.
How to restore an archived scan
Click Restore file details on the Files tab. Restore usually takes a few seconds; scans with around a million items can take closer to half a minute. MigrationFox fetches the archived copy, puts the per-file rows back, clears the Archived badge, and the page reloads with the full list.
Once restored, the migration behaves normally. If it then sits idle past its retention threshold again, it's archived again, and you can restore it again.
Restore is free
Restoring costs nothing, doesn't use migration credits, and you can restore the same migration as often as you like.
Resume, Retry, and other job actions
You don’t need to click Restore file details before Resume or Retry. Both restore the archived file detail automatically before the migration continues, so the first progress update can take a few seconds longer. There is no extra prompt.
If the automatic restore fails, the action stops with Could not restore archived scan data. Try again in a moment. Try again; if it keeps happening, contact support with the job ID.
Can I archive or opt out manually?
No. Archiving runs on the same schedule and thresholds for every workspace, and there is no setting to archive a migration early or to keep one from being archived. The only manual action is Restore file details, which you can use at any time.
Technical details
- Where it goes: MigrationFox's cold storage on Azure Blob Storage (Cool tier), one compressed file per migration.
- What it contains: the per-file scan items and per-file migration results. A restore puts back the same rows that were archived.
- File contents are not archived. The archive holds only the file list and per-file status (names, paths, sizes, dates, results).
- Schedule: once a day at 03:00 UTC, up to 100 migrations per run, oldest first.
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Files tab is empty and there's no Restore button | The migration isn't archived. It genuinely has no files (for example, a scan of an empty folder). | Check the summary. If the file count is 0, the empty Files tab is correct. |
| Clicking Restore shows "Restore failed. Try again, or contact support@migrationfox.com." | The restore couldn't finish (network problem or a temporary error). | Wait a moment and try again. If it keeps failing, contact support with the job ID. |
| Restore takes longer than usual | The scan has a very large number of items. | Wait. Million-item scans can take around half a minute. If it takes much longer, contact support. |
| A migration shows "Archived" right after it finished | Not expected under the thresholds above (the shortest is 1 day, for canceled migrations). | Contact support with the job ID. |
| Resume or Retry stops with "Could not restore archived scan data" | The automatic restore hit an error. | Try the action again. If the error repeats, contact support with the job ID. |
If restore repeatedly fails
Contact support at support@migrationfox.com with the job ID. We can look at the archived copy and restore it from our side.
FAQ
Does my scan data get deleted?
No. Archiving is not deletion. The migration's summary stays in place, and its per-file detail is kept in cold storage until you delete the migration. You can restore it at any time.
Do I pay for restored data?
No. Restoring is free, doesn't use migration credits, and has no limit on how many times you restore the same migration.
How long does restore take?
Usually a few seconds. Scans with around a million items can take closer to half a minute. If it regularly takes much longer, contact support with the job ID.
Can I opt out of archiving?
No. Archiving applies to every workspace with the same thresholds. Retrying or resuming a migration resets its idle clock, and running or paused migrations are never archived.
Will Resume or Retry fail because the scan is archived?
No. Resume and Retry restore the archived detail automatically before continuing. You won’t be prompted; the first progress update may take a few seconds longer.
What happens if I delete the migration?
Deleting a migration removes it from your account, including its file details, and its archived file details can no longer be restored. Deletion can’t be undone, so keep the migration if you may need its file list later.
Do archived file lists include my files?
No. Only the file list and per-file results are archived (names, paths, sizes, dates and status). File contents are not part of the archive.
Related
- Rollback preview: remove the files a completed migration created
- Revoke share links: lifecycle controls on Client Live View URLs