MigrationFox Docs

Windows app for IT admins

How to license, lock down and allow MigrationFox for Windows through your firewall: license keys, offline license files, machine policies, installer options and the network address list.

Short version

Install with STRICT=1 and a license key, and the PC keeps job data on the PC, never signs in to MigrationFox, and contacts MigrationFox only to renew its license with a hash of its machine ID. For a PC with no internet, use an offline license file instead. The Trust page has the step-by-step checklist.

This PC only (Strict mode)

Settings → Migrations → Where job data is kept → This PC only, or the Connectivity policy set to Strict, turns on Strict mode:

License keys

A license key (it starts with csl_) licenses a PC that doesn’t sign in to MigrationFox. It can only renew that PC’s license: it can’t start, see or change anything on MigrationFox web.

  1. On MigrationFox web, open Devices and create a license key. It is shown once; MigrationFox keeps only a hash of it. The key uses the MigrationFox Pro seat of the person who created it.
  2. On the PC, paste it in Settings → General → License (shown when This PC only is on), or pass it to the installer with LICENSEKEY (see Installer options). The installer hides the key from its log.

The PC renews 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 key and the machine ID (a SHA-256 hash of the Windows MachineGuid, not the GUID itself). On the free trial, outside Strict mode, it also sends the totals copied and InfoPath forms archived on the PC and when the trial was first used. Nothing else. To stop a key working, remove it on the Devices page.

Offline license files

For a PC that can’t reach MigrationFox at all:

  1. On the PC, find its machine ID: Settings → General → License, or Get-MFPcLicense | Select-Object MachineId in PowerShell. It is 64 letters and digits.
  2. On any computer with internet, open Devices on MigrationFox web, choose Create an offline license, and enter a name and the machine ID. You get a license file signed by MigrationFox.
  3. Carry the file to the PC and import it: Settings → General → License, or Import-MFPcLicense -Path E:\MigrationFox-license-PC1.json. The PC keeps the file only if MigrationFox signed it, it is for this PC and it is still valid.

An offline license needs MigrationFox Pro with a free seat (the free trial needs the PC to go online). It is valid until your MigrationFox Pro renewal date plus 7 days of grace; then make a new one. It is checked on the PC against MigrationFox’s public key, and nothing is sent. The license is checked when a migration starts, so a migration that has started always finishes.

Sign in with your organization's app registration

When to set it up: only if your organization blocks third-party apps, so an admin can't approve MigrationFox on Microsoft's consent screen. If your admin can approve MigrationFox, leave it off. It is in Settings, Help, under Advanced, and it lists the redirect address and the delegated permissions to add. It uses no secret: only your app's ID and your tenant are saved on the PC, after a test sign-in shows the app grants what is needed.

It covers "Sign in with Microsoft" for SharePoint and OneDrive connections on the PC, and the migrations that use them:

It does not cover:

Machine policy settings

Set these as string (REG_SZ) values under HKLM\Software\Policies\MigrationFox, for example with Group Policy or Intune. A value set by policy can’t be changed in the app, and the app never reads these from HKCU.

ValueSettingsWhat it does
ConnectivityStrict or StandardStrict turns on Strict mode (above): license renewal only, job data on the PC, update checks off.
JobDataLocationThisPC or CloudWhere new migrations keep their job data: this PC only, or MigrationFox web.
JobDataSyncOff or CountsFor migrations kept on the PC outside Strict mode: Counts sends their kind, status and file and size counts to the web dashboard (never names, paths, errors or logs). Off sends nothing.
UpdateCheckOffTurns off update checks. Strict mode already does.

The license key is not a policy value: set it with the installer option LICENSEKEY or in the app.

Installer options

Both installers take the same options. The installer contacts nothing.

msiexec /i MigrationFox-Setup.msi /qn STRICT=1 DATALOCATION=ThisPC LICENSEKEY=csl_...

MigrationFox-Setup.exe /S /STRICT=1 /DATALOCATION=ThisPC /LICENSEKEY=csl_...
OptionWhat it does
STRICT=1Sets Connectivity to Strict.
DATALOCATION=ThisPC or CloudSets JobDataLocation.
LICENSEKEY=csl_...Saves the license key on the PC. A value that doesn’t start with csl_ is ignored.

The MSI, and the .exe installed for Anyone using this computer, write STRICT and DATALOCATION as the machine policies above. The .exe installed Only for me saves them as that user’s own settings instead, which the user can change.

Network address list

Everything is outbound HTTPS on port 443. No inbound ports are open to the network. The background service listens on 127.0.0.1 (this PC only). On the PC, Get-MFNetworkRequirement lists what the PC contacts as it is set up now, why, and what is sent; Get-MFNetworkRequirement -All lists every entry. The app shows the same list in Settings → Network.

AddressWhyIn Strict mode
login.microsoftonline.comMicrosoft sign-in for connections made on the PC, and token renewalUsed
graph.microsoft.comReading and writing files, folders, people and sitesUsed
*.sharepoint.comSharePoint and OneDrive: listing, uploading, True History import, folder dates and peopleUsed
*.blob.core.windows.netTrue History only: temporary storage SharePoint provides in your own tenant for Microsoft’s importUsed for True History
api.migrationfox.comLicense renewal (not needed with an offline license file)Used
api.migrationfox.comPC status, migrations kept on MigrationFox web, account and connections shown in the app, counts for migrations kept on the PC (only if chosen), problem reports you sendNot used
app.migrationfox.comUpdate check, and signing in to MigrationFox in your browserNot used
www.googleapis.com, oauth2.googleapis.comGoogle Drive, only when migrating from or to itNot used
api.dropboxapi.com, content.dropboxapi.comDropbox, only when migrating from or to itNot used
api.box.com, upload.box.comBox, only when migrating from or to itNot used
slack.com, files.slack.comSlack, only when migrating from itNot used
*.amazonaws.com, or the address of your S3-compatible storageAmazon S3, only if you add an Amazon S3 connection. Its keys are kept on the PCUsed only with an Amazon S3 connection
*.blob.core.windows.netAzure Blob, your own storage account, only if you add an Azure Blob connection. Its key is kept on the PCUsed only with an Azure Blob connection
Your SFTP server (port 22 unless you set another)SFTP, only if you add an SFTP connection. Its password or key is kept on the PCUsed only with an SFTP connection

Only the worldwide Microsoft 365 cloud is supported; GCC High and DoD are not. File shares are read over your own network.