Trust Center
How MigrationFox handles your data
The short, plain version of where your files go, what we keep, what we ask Microsoft for, and what we have and haven’t been certified for. The detail lives in our security overview, DPA and subprocessor list.
Start with how you run MigrationFox
MigrationFox web
Migrations run in our cloud
File contents stream through our worker in Canada and aren’t kept. Job details and encrypted sign-ins are kept in our database in the United States.
Where your files go →
MigrationFox for Windows, isolated
Migrations run on your PC or server
Files go straight from your source to your destination. With job data kept on This PC only, job details and sign-ins stay on the PC, and the only call to MigrationFox is the license renewal.
Setup checklist for IT →
MigrationFox for Windows, isolated
Company and compliance
Where your files go
Every migration follows the same steps: connect, scan, move, verify. What changes is where the file bytes travel. On MigrationFox web, cloud migrations run in the MigrationFox cloud, and file shares and on-premises SharePoint go through a File share agent on a server in your network, which sends files from the share straight to the destination. In MigrationFox for Windows, every migration runs on a PC or server you control.
MigrationFox web: file contents go from your source to the MigrationFox migration worker on Oracle Cloud, which streams them to your destination and does not keep them after the migration. MigrationFox for Windows: file contents go from your source to your own PC or server and then to your destination, without passing through MigrationFox. By default, MigrationFox stores job status, counts, file names and paths, errors, your connection credentials encrypted with AES-256, and the activity log, in an operational database hosted in the United States. In MigrationFox for Windows, set Where job data is kept to This PC only and job data and sign-ins stay on the PC; MigrationFox stores nothing about those migrations.
On MigrationFox web
- · File contents stream through our migration worker in Toronto, Canada (Oracle Cloud, Canada Southeast region), from your source straight to your destination.
- · We don’t retain file contents after a migration completes.
- · We keep operational metadata (file paths, sizes, success or failure status, and the audit log) plus your encrypted credentials. That metadata is processed on infrastructure in the United States (Railway, us-west-2), and MigrationFox Inc. remains accountable for it under PIPEDA.
In MigrationFox for Windows
- · The app runs on a Windows machine you control. It reads from your source and writes to your destination directly from that machine, so file contents don’t pass through MigrationFox servers.
- · By default (job data kept on MigrationFox web), MigrationFox web receives job metadata so you can track the job on the web dashboard: progress, file paths and names, sizes, status, the names and email addresses used for Created By and Modified By, and the job log with any error messages. File contents are not sent.
- · Set Where job data is kept to This PC only and the only call to MigrationFox is the license renewal. The setup checklist below walks through it.
- · It talks to MigrationFox over outbound HTTPS only, with no VPN. No inbound ports are open to the network. The background service listens on 127.0.0.1 (this PC only).
- · For Microsoft, Google, Box and Dropbox sign-ins made on MigrationFox web, the app receives short-lived access tokens. Refresh tokens and client secrets stay encrypted on the MigrationFox side. Key-based connections (such as S3, Azure Blob or SFTP) are sent to your paired app over HTTPS, because the protocol needs the key.
MigrationFox Inc. is a Canadian federal corporation (CBCA) and follows PIPEDA, Canada’s federal privacy law. The MigrationFox for Windows page compares the two products.
MigrationFox for Windows, isolated
Setup checklist for IT and security teams
Four steps to run migrations on your own PC or server with nothing about them leaving your network. Each step says how to check it. You need MigrationFox Pro (the 14-day trial includes it).
When all four steps are done
- · File contents go from your source to your destination without passing through MigrationFox.
- · File lists, logs, job details and sign-ins stay on the PC. Job details and file lists are encrypted with Windows. Logs stay on this PC and are cleaned up after 30 days.
- · The only call to MigrationFox is the license renewal: a hash of the machine ID, every 12 hours (every 5 minutes while the PC has no working license). With an offline license file, not even that.
- · Nobody on the PC can change these settings.
-
Keep job data on the PC
In the app: Settings → Migrations → Where job data is kept. Two choices:
Choice What goes to MigrationFox What you give up MigrationFox web (default) Job details, so migrations can also be followed on the web dashboard, including the status and counts of migrations kept on the PC. License renewal. Update checks. Nothing This PC only Only the license renewal: a hash of the machine ID. File lists, logs and job details stay on the PC (job details and file lists are encrypted with Windows; logs are cleaned up after 30 days), and SharePoint and OneDrive sign-ins made on the PC stay there too. Following these migrations on the web dashboard. Google Drive, Dropbox, Box, Slack and Amazon S3 (This PC only covers SharePoint, OneDrive and file shares). Update checks. Sending problem reports (save them to a file instead). Signing in to MigrationFox on the PC: a PC signed in before keeps renewing with that sign-in, sending only the machine ID; any other PC uses a license key. Check: with This PC only, the PC’s migrations don’t appear on the MigrationFox web dashboard, and
Get-MFNetworkRequirementlists only the addresses in step 3. -
Lock the settings with policy
Set them when you install, so nobody on the PC can change them. Both installers take the same options:
msiexec /i MigrationFox-Setup.msi /qn STRICT=1 DATALOCATION=ThisPC LICENSEKEY=csl_... MigrationFox-Setup.exe /S /STRICT=1 /DATALOCATION=ThisPC /LICENSEKEY=csl_...The license key comes from the Devices page on MigrationFox web and is hidden from the installer log. The installer contacts nothing. Or set the values yourself under
HKLM\Software\Policies\MigrationFox, for example with Group Policy or Intune:Value (string) Setting Same as ConnectivityStrictorStandardStep 1: Strictlimits the PC to the license renewal, as with This PC onlyJobDataLocationThisPCorCloudStep 1: This PC only, or MigrationFox web JobDataSyncOfforCountsWhether the status and counts of migrations kept on the PC go to the web dashboard UpdateCheckOffTurns off update checks (This PC only already does) Check: in Settings, the options set by policy can’t be changed.
Every value, installer option and address: Windows app for IT admins in the docs.
-
Allow these addresses in your firewall
With This PC only, the PC contacts only these, all outbound HTTPS on port 443, with no VPN. No inbound ports are open to the network. The background service listens on 127.0.0.1 (this PC only). File shares are read over your own network.
Address Why login.microsoftonline.comMicrosoft sign-in for your tenant graph.microsoft.comReading and writing files, folders, people and sites in your Microsoft 365 *.sharepoint.comYour SharePoint and OneDrive *.blob.core.windows.netOnly for True History: temporary storage SharePoint provides in your own tenant for Microsoft’s import api.migrationfox.comLicense renewal. Not needed with an offline license file. Check: on the PC, in PowerShell,
Get-MFNetworkRequirementlists every address it contacts as it’s set up now, why, and what is sent. -
License the PC
Use the license key from step 2, or for a PC that can’t reach MigrationFox at all, download an offline license file from the Devices page. The PC checks it against our public key until the date written in it, with no renewal. What the license server keeps lists everything a renewal leaves with us.
Check: the PC shows as licensed in the app, and on your Devices page (unless it uses an offline license file).
More on the Windows app: MigrationFox for Windows. Questions about your setup: security@migrationfox.com.
What the license server keeps
A PC that keeps its migrations on the PC still renews its MigrationFox Pro license with us: at start, every 12 hours, and every 5 minutes while it has no working license. Each renewal is one HTTPS request to api.migrationfox.com with the PC’s sign-in or license key, and a body that holds only:
- · Machine ID: a SHA-256 hash of the Windows MachineGuid, not the GUID itself. In Strict mode (This PC only), this is all it sends.
- · Only on the free trial, outside Strict mode: the totals copied (bytes) and InfoPath forms archived on this PC, and when it first used the trial. A PC with MigrationFox Pro never sends them.
No host name, user name, file names, paths or job details are in the renewal. This is everything we keep, and for how long.
| What | Why | How long |
|---|---|---|
| Machine ID: a SHA-256 hash of the Windows MachineGuid, not the GUID itself | Ties the license to that PC | Until the PC is removed from your workspace, or the workspace is deleted |
| Time of the last renewal | Shows the PC as active on your Devices page | Same as above |
| The PC’s name. It comes from signing in to MigrationFox on the PC (the Windows host name) or from the name you give a license key on the Devices page, not from the renewal. Outside Strict mode, the app’s status updates report a hash of the name instead when job data is kept on the PC | Lets you tell your PCs apart | Same as above |
| During the free trial only: how much of the trial allowance the PC has used, and when it started | Enforces the trial allowance | Same as above |
| The IP address and time of each renewal request, in our hosting provider’s request logs | Security and troubleshooting | Up to 90 days, then deleted automatically by our hosting provider |
We never receive the PC’s file names or paths, people’s names, sign-ins or job details for migrations kept on the PC. An offline license file needs no renewal at all: it is checked on the PC against our public key until the date written in it.
Windows app updates and installer checks
You decide when MigrationFox for Windows updates. With job data kept on MigrationFox web, the app checks for a new version and asks before installing it. With This PC only, it never checks, so your IT team installs each update. Either way, every release is listed with its notes and the SHA-256 hash of each installer.
Watch for new releases
The release list is a JSON file your monitoring can watch: app.migrationfox.com/desktop/releases.json. Newest first, with the version, release date, release notes and installer hashes. Release notes mark security fixes with “Security:”.
Download the current installer →Check an installer before you run it
In PowerShell, in the folder with the installer:
Get-AuthenticodeSignature .\MigrationFox-Setup.exe
Status should be Valid, signed by CN=MigrationFox Inc, O=MigrationFox Inc, L=Oakville, S=Ontario, C=CA.
Get-FileHash .\MigrationFox-Setup.exe -Algorithm SHA256
The hash should match the one listed for that version.
Encryption and sign-in
Credentials and data in transit
- · OAuth tokens, service-account keys and agent secrets are encrypted at rest with AES-256 (GCM mode), using a server-side key that is never stored alongside the encrypted data.
- · The credential format supports versioned keys, so encryption keys can be rotated without losing access to existing connections or asking you to reconnect.
- · Traffic to the MigrationFox API and to cloud platforms uses TLS (HTTPS). File share reads from the Windows app stay on your own network.
Your MigrationFox account
- · Passwords are hashed with Argon2id; older accounts upgrade automatically on next sign-in.
- · Multi-factor authentication (TOTP, with recovery codes) is available on every account.
- · Sessions are scoped to a single tenant and role, with no cross-tenant token reuse.
- · Sign-ins, credential changes, jobs, governance scans and admin actions are written to a tenant-scoped activity log.
Permissions in plain English
We use four separate Microsoft Entra apps, all published by MigrationFox Inc., so each consent screen asks only for what that product needs. You connect only the apps for the products you use. For each one: what it asks for, why, which features use it, and how to take the access back.
MigrationFox (file and site migration)
Used when you choose “Sign in with Microsoft” to connect SharePoint or OneDrive as a source or destination. Delegated Microsoft Graph permissions, so it acts as the person who signs in:
Files.ReadWrite.All Sites.Manage.All Sites.ReadWrite.All Group.ReadWrite.All User.Read User.Read.All offline_access
- · Why: a migration reads files from the source and creates sites, libraries, folders and files in the destination.
Group.ReadWrite.Allcreates the Microsoft 365 group behind a new team site.User.Read.Allmaps people between tenants so authors and permissions land on the right accounts.offline_accesslets a long migration keep running after the first hour. - · Features: SharePoint and OneDrive migrations, bulk site provisioning, restructuring, user mapping.
- · Optional extras, admin-granted: SharePoint
AllSites.FullControlfor True History (original authors, dates and versions), andTermStore.ReadWrite.Allfor creating managed metadata term sets. Only the features that need them use them. - · Instead: you can connect with your own app registration.
MigrationFox Mail (mailbox migration, private beta)
Mail-only permissions, kept in their own app so file consent never includes mail:
Mail.Read Mail.ReadWrite User.Read offline_accessMail.ReadWrite User.Read.All- · Why:
Mail.ReadWritereads messages from a source mailbox and writes them into a destination mailbox.User.Read.Alllists the mailboxes in your organization so you can pick which ones to move. - · Features: mail migration only.
MigrationFox Assessment (governance report packs)
Read-only. The assessment client only sends read (GET) requests to Microsoft Graph: it has no write methods, and any attempt to send PATCH, POST, PUT or DELETE is stopped with an error before it leaves our code. The base set is 15 read-only Graph permissions:
Sites.Read.All Files.Read.All User.Read.All Group.Read.All Directory.Read.All AuditLog.Read.All InformationProtectionPolicy.Read.All Policy.Read.All Reports.Read.All SecurityEvents.Read.All TeamSettings.Read.All SharePointTenantSettings.Read.All DelegatedPermissionGrant.Read.All Application.Read.All RecordsManagement.Read.All
- · Why: each report pack reads tenant settings, sharing, labels, sign-in policies, apps and usage to produce its findings. What each permission is used for, check by check: What we check.
- · Sign in with Microsoft vs. your own app: the sign-in consent asks for 11 of these plus
offline_access. The other four (AuditLog.Read.All,InformationProtectionPolicy.Read.All,Reports.Read.All,DelegatedPermissionGrant.Read.All) are used as application permissions, which means connecting with your own app registration (client credentials). Checks that lack a permission are reported as not verified, rather than failing the assessment. - · Deeper modules: some add read permissions such as
Team.ReadBasic.All,TeamMember.Read.All,Channel.ReadBasic.All,RoleManagement.Read.DirectoryandIdentityRiskyUser.Read.All. The SharePoint Advanced Management module usesSites.FullControl.All, because Microsoft only exposes some per-site settings under that permission. The read-only guard still applies. - · Features: governance and Copilot readiness report packs, and the free snapshot.
MigrationFox Teams (Teams migration)
Microsoft’s Teams import API only accepts application permissions, so a Teams connection is approved once by a tenant admin (admin consent) instead of by each user. Application permissions:
Teamwork.Migrate.All ChannelMessage.Read.All Channel.ReadBasic.All Team.ReadBasic.All TeamMember.ReadWrite.All User.Read.All Group.ReadWrite.All Sites.ReadWrite.All
- · Why: read channels and messages from a source team, create the destination team, import messages under the right authors, add members and owners, and copy channel files.
- · Features: Slack to Teams and Teams to Teams migrations.
- · Note: reading channel messages with application permissions also needs Microsoft’s approval for its protected Teams APIs. That approval is pending for the MigrationFox Teams app, so reading a Teams source with it may be refused until it is granted. You can also connect Teams with your own Azure app instead.
How to revoke access
- In MigrationFox: delete the connection on the Connections page. That removes the encrypted tokens or keys we hold for it. Job history stays. A connection that an active migration is using can’t be deleted until that migration is cancelled or finished.
- In your tenant: in the Microsoft Entra admin center, go to Enterprise applications, open the app (MigrationFox, MigrationFox Mail, MigrationFox Assessment or MigrationFox Teams), then Properties, then Delete. That removes the app and every consent granted to it in your tenant.
- To limit who can use an app instead of removing it: on its Properties page set “Assignment required” to Yes, then choose the allowed people under Users and groups.
Verified publisher and signed installer
Microsoft Verified Publisher
When you connect a Microsoft 365 tenant, the consent screen shows “MigrationFox Inc” with Microsoft’s blue verified-publisher checkmark. If you ever see a MigrationFox consent screen without it, don’t approve it. Email security@migrationfox.com.
Code-signed Windows app
The Windows installer and the app inside it are signed with Azure Trusted Signing, so Windows SmartScreen identifies the publisher instead of warning about an unknown one.
Download for Windows →Subprocessors and DPA
The vendors that help us run the service. Each is contractually bound to handle data only on our instructions. We email customers at least 30 days before adding or replacing one.
| Subprocessor | Purpose | Region |
|---|---|---|
| Oracle Cloud Infrastructure | Migration worker (file content streaming, not retained) | Canada Southeast (Toronto) |
| Railway | API hosting, Postgres database, Redis queue | United States (us-west-2) |
| Vercel | Website, web app and docs hosting | Global edge network |
| Stripe | Payment processing | United States |
| Resend | Transactional email | United States |
| Sentry | Error tracking | United States |
| Microsoft Azure | Trusted Signing for the Windows installer | United States (East US) |
The maintained list, with data categories: Subprocessors. Our standard Data Processing Agreement covers GDPR Article 28, UK GDPR and PIPEDA; email legal@migrationfox.com to sign one.
Compliance status and disclosure
Certifications
We do not currently hold SOC 2 or ISO 27001 certification. If we obtain independent audit reports, our DPA commits us to making them available to customers. Until then, we answer security questionnaires and your auditors can review this page, the DPA and our security overview.
Reporting a vulnerability
Email security@migrationfox.com. We acknowledge reports within one business day and aim to validate or dismiss them within five.
Questions from your security team?
Send them to security@migrationfox.com, or start with 2 GB free and see it for yourself.