Frequently asked questions

Three things on one platform:

• Cloud migration — files, mailboxes, Teams channels, and SharePoint sites across 13 platforms (Google Drive, SharePoint, OneDrive, Dropbox, Box, AWS S3, Azure Blob, SFTP, SMB, Teams, Slack, Gmail, Exchange).
• M365 governance — six read-only assessments that score tenants on a 1.0–4.0 scale for Copilot readiness, Power Platform posture, SharePoint / OneDrive oversharing, Teams sprawl, and M365 security.
• Archival and modernization — InfoPath PDF archive (before the July 2026 retirement) and a SharePoint modernization scan that inventories legacy workloads.

Free tier is 2 GB of migration, no credit card, forever. Every connector works on the free tier. Beyond that:

• Migration — $0.50/GB pay-as-you-go (CAD). Credits never expire.
• M365 assessment — $399 CAD single-assessment, 90-day access, locked to one tenant.
• M365 Complete bundle — $1,599 CAD, all six assessments, white-label PDF, commercial redistribution license.
• InfoPath PDF archive — $0.15 per form.

Free governance snapshot for any one assessment per month, per tenant. Enough to decide whether to buy.

No. The free tier requires email only. Payment information is only collected when you purchase migration credits or a governance assessment.

Google Drive / Workspace, SharePoint Online, OneDrive for Business, Microsoft Teams, Slack, AWS S3, Azure Blob Storage, Dropbox, Box, SFTP / FTP, SMB / Windows file shares, Gmail, and Exchange Online. Full list and per-platform setup guides live at migrationfox.com/platforms.

Three good paths depending on your project:

• Take the product tour — end-to-end walk-through of the five phases.
• Browse use cases — scenario-first starting points.
• Just start — sign up, connect a source, run a discovery scan. You can experiment on the free tier before committing.

Most typical migrations finish in minutes. MigrationFox runs many concurrent file streams with auto-split partitioning for large jobs, so throughput scales with tenant capacity. Large runs (10,000+ files) are automatically parallelised across workers. Migration Rehearsal gives you a runtime prediction before the real run.

Failed items are auto-retried with exponential backoff. If a job is interrupted, restart picks up where it left off — no re-transferring completed files. Persistent failures produce an emailed error report with per-file detail.

Yes. SharePoint → SharePoint, Google Drive → Google Drive, Teams → Teams, Dropbox → Dropbox. Useful for tenant consolidations, M&A, and information-architecture fixes (e.g., mega-site restructuring).

Yes. Source permissions are enumerated during discovery, principals are mapped to destination users or groups, and the mapping is applied post-copy. For cross-tenant migrations, upload a CSV mapping of source UPN to destination UPN. Rehearsal flags any principal that cannot be mapped so you decide before the real run.

Yes, for SharePoint destinations. Enable SPMT True History Mode on the migration and the original Created, Modified, CreatedBy, and ModifiedBy fields are preserved instead of replaced with the service account and run time. Reference.

Yes. A lightweight Windows agent runs inside your network with SMB access to the file share. No inbound firewall ports — the agent polls for jobs outbound. The agent self-updates between jobs. Agent docs.

Yes. Full Teams → Teams migration including channels, messages with original timestamps, thread replies, and channel files. Destination teams are auto-created if they do not exist. User mapping matches source speakers to destination accounts.

A full dry-run of every phase of the real migration, with destination writes short-circuited. It produces a verdict pill (ready / caveats / do not proceed), a runtime prediction, a Graph API request-count forecast, and a 10-category issue report covering every class of cutover failure we have seen. Deep dive.

Yes, for seven days after the migration completes. Before reverting, a preview shows exactly what will be undone — file counts, permission removals, folder deletions. If the preview looks right, one click rolls back. The window is seven days because that is long enough to notice a landing problem and short enough to keep the journal size bounded. Reference.

No user file data is stored on MigrationFox servers. Content streams directly from source to destination. What is stored is the project configuration, the discovery inventory (metadata only — filenames, sizes, permission mappings), the rehearsal journal, and the seven-day rollback journal.

Credentials are encrypted at rest with AES-256-GCM. Passwords (for the MigrationFox account itself) are hashed with Argon2id. OAuth tokens are rotated automatically.

Yes. Every assessment is 100% read-only. A write guard enforced at the Graph API client level makes PATCH, POST, PUT, and DELETE physically impossible — the SDK refuses to issue them. Only read-only Graph scopes are consumed, and a scope-diff UI tells you exactly which consents are missing before the scan runs.

Fourteen read-only Microsoft Graph scopes, admin-consented once. The exact list is shown in the scope-diff UI before you purchase or run the assessment. No write scopes, no user-impersonation scopes.

Yes. Share links are revocable instantly from the project dashboard. The JWT has a 30-day default expiry, but you can shorten it per link or revoke the entire link on demand. Revocation reference.

All six assessments — Copilot Readiness, Power Platform, SharePoint & OneDrive, Teams, M365 Security, plus the cross-cutting M365 Complete report. One-time $1,599 CAD, 90-day access, locked to one tenant. Includes a white-label PDF (your logo, no MigrationFox branding) and a commercial redistribution license to deliver the report to a paying client.

Any assessment can be scheduled to re-run monthly. Each run produces a composite score, plotted on a trend chart over time. Findings are diffed — new, resolved, and persistent findings are broken out. You get an email alert the moment a new Must-Do-Before-Copilot finding appears. Full write-up.

Yes, with the M365 Complete bundle tier. The bundle includes a commercial redistribution license that allows you to charge a client for delivery of the report. Brand the PDF with your logo and colour, remove MigrationFox branding, and hand it to the client.

Yes. Every action you can take in the product can be driven via REST API with a personal access token. Webhooks fire on job state changes. See the API reference.

Yes. One MigrationFox account can connect multiple M365 tenants and multiple Workspace organisations. Each project is scoped to a source / destination pair. Billing is per-account; per-client delivery uses white-label PDF and the bundle license.

They never expire. Purchase a bundle, use it over months or years — whatever you do not use this migration is there for the next one.

Email support@migrationfox.com. For feature requests, feedback@migrationfox.com. Response time is within one business day; during active migrations, usually same-hour.

Email support@migrationfox.com with the job ID (run_*) if it is migration-related, or the assessment run ID if it is governance-related. The project URL helps too.