Move and govern your Microsoft 365 and cloud content.

Here’s how MigrationFox protects your data, where it’s processed, and what you control.

Sign-in details for the platforms you connect are encrypted with AES-256 at rest, and account passwords are hashed with Argon2id. Multi-factor authentication is available on every account, and sign-ins, credential changes and migrations are recorded in an activity log for your account.

When you run a migration from the Windows app on your own PC or server, files go straight from the source to the destination; MigrationFox sees status, counts, file names and paths, and errors. When you run it in the MigrationFox cloud, files stream through our migration worker and are not stored after the migration. InfoPath forms are the one exception: each form is sent to MigrationFox to be rendered into a PDF.

Governance assessments use a separate read-only app that blocks every write. The Trust Center covers hosting locations, subprocessors and certification status.

13 platforms: SharePoint, OneDrive, Google Drive, Dropbox, Box, Amazon S3, Azure Blob Storage, SFTP, Windows file shares (SMB), Microsoft Teams, Slack, Gmail and Microsoft 365 mail (Exchange). Gmail and Microsoft 365 mail migration are in private beta. See every platform.

It’s free to start: signup includes 2 GB of migration credits, no credit card, and they never expire. After that you can pay as you go with credits that never expire, or get unlimited migrations from the Windows app with an annual license. Governance reports and InfoPath archiving are one-time purchases. Current prices are on the pricing page.

It depends mostly on the source and destination APIs, file sizes and file counts. MigrationFox runs many file streams in parallel, and in the MigrationFox cloud, jobs with 1,000 or more files split into 3 partitions that run side by side. Small jobs often finish in minutes, and you can run several jobs at once. A free scan shows the size of the job before you start.

Yes. MigrationFox supports same-platform migrations: SharePoint to SharePoint, Google Drive to Google Drive, and so on. This is useful for tenant consolidations, reorganizations, or moving data between personal and shared drives.

Yes. The MigrationFox Windows app (code-signed) reads SMB file shares on your network with your own Windows account and moves files straight to your chosen cloud destination over outbound HTTPS, with no inbound firewall ports. It installs without admin rights, and Background mode keeps it running with nobody signed in (file shares are then read with the computer’s account). File dates are kept; file share (NTFS) permissions are not migrated, so set access on the destination.

Failed files are automatically retried with exponential backoff. If a job is interrupted, you can resume it from where it left off, with no need to re-transfer files that already completed. Failed jobs, and the failed files of a finished job, are retried automatically later when the errors look temporary (up to three more times), and you get an email with an error summary and a link to the per-file log if a job still fails.

Yes, with one caveat. MigrationFox imports channel conversations into Microsoft Teams with their original timestamps and thread replies, creates the destination teams, adds members and owners, and posts messages as the mapped people. Slack to Teams works today. For Teams to Teams, Microsoft requires separate approval for any app that reads channel messages from the source tenant; that approval for the MigrationFox Teams app is pending, so talk to us before you plan a Teams-to-Teams move.

Yes. SharePoint site migration copies document libraries with files, lists with items and columns, and lets you select exactly what to migrate. Metadata and column definitions are preserved in the destination.