MigrationFox Documentation

Supported Platforms

How It Works

Every migration follows five core steps:

Quick Start Guide

Get your first migration running in just a few steps.

Creating a Project

A project is the top-level container for a migration. Each project has its own source connection, destination connection, discovery data, and migration jobs.

Project Settings

Project Lifecycle

A project goes through these stages:

1. Setup — Connect source and destination, configure credentials
2. Discovery — Scan the source to build a file inventory
3. Provisioning — Optionally pre-create destination structure (sites, libraries, folders)
4. Migration — Transfer files and metadata
5. Verification — Review results, re-run for any failed items

Understanding the Workflow

Every migration in MigrationFox follows a five-phase workflow. Understanding each phase helps you plan and execute migrations efficiently.

Phase 1: Connect

Authenticate with your source and destination platforms. MigrationFox supports OAuth (interactive login), service accounts (for unattended access), and API keys depending on the platform. Credentials are encrypted with AES-256 and stored securely.

Phase 2: Discover

Discovery scans your source environment and builds a complete inventory of files, folders, and metadata. The discovery report shows:

• Total file count and size
• Folder tree structure
• File type distribution
• Large files that may need special handling
• Permission mappings

Phase 3: Provision

Before migrating data, MigrationFox can pre-create the destination structure. For SharePoint, this means creating site collections, document libraries, and folders. For Google Drive, this means creating Shared Drives and folder hierarchies. Provisioning ensures the destination is ready to receive data.

Phase 4: Migrate

The actual data transfer. MigrationFox streams files directly from source to destination without storing data on its own servers. Files are transferred in parallel with configurable concurrency. Large files use chunked/multipart uploads for reliability.

Phase 5: Monitor

Track migration progress in real time. The dashboard shows:

• Files transferred / remaining / failed
• Transfer speed (MB/s)
• Estimated time remaining
• Per-file status with error details
• Audit log of all operations

Google Drive / Google Workspace

Migrate files and folders to or from Google Drive, including personal drives, Shared Drives (Team Drives), and domain-wide content for Google Workspace organizations.

Prerequisites

• A Google Cloud project with the Google Drive API enabled
• For organization-wide access: a Google Workspace admin account (for domain-wide delegation)
• Either a service account (recommended for production) or an OAuth 2.0 client

Required Permissions / Scopes

This scope grants full read/write access to Google Drive files. For read-only source access, you can use drive.readonly instead.

Service Account Setup (Recommended)

Service accounts provide unattended, organization-wide access without requiring individual user authentication.

OAuth Setup (Alternative)

OAuth is simpler to set up but requires interactive user login and only accesses that user's content.

1. In Google Cloud Console, go to Credentials → Create Credentials → OAuth Client ID
2. Application type: Web application
3. Add your MigrationFox redirect URI: https://app.migrationfox.com/auth/google/callback
4. Note the Client ID and Client Secret
5. In MigrationFox, choose OAuth authentication and click Connect with Google

Supported Features

SharePoint / OneDrive

Migrate files, document libraries, and site content to or from SharePoint Online and OneDrive for Business.

Prerequisites

• An Azure AD (Entra ID) app registration
• A Microsoft 365 tenant with SharePoint Online
• Global Admin or SharePoint Admin permissions (for granting consent)

Required Permissions

For Application (app-only, unattended) access:

App Registration Setup

OAuth Setup (Delegated Access)

For delegated access (user-specific), add Delegated permissions instead of Application permissions, add your redirect URI (https://app.migrationfox.com/auth/microsoft/callback), and use the OAuth flow in MigrationFox.

Supported Features

Microsoft Teams Coming Soon

Migrate Teams channels, messages, replies, reactions, and member lists. The Teams connectors are built and the migration processor is in progress.

Prerequisites

• An Azure AD app registration (can be the same as your SharePoint registration, or separate)
• Teams Administrator permissions for granting consent

Required Permissions

Setup

Supported Features

Slack Coming Soon

Migrate Slack channels, messages, threads, reactions, and file attachments. The Slack source connector is built with Microsoft Teams as the destination.

Prerequisites

• A Slack app with a bot token
• Workspace Admin or Owner permissions (for installing the app)

Required Bot Token Scopes

Setup

Supported Features

AWS S3

Migrate files to or from Amazon S3 buckets. Also works with S3-compatible storage providers like MinIO, Wasabi, and Backblaze B2.

Prerequisites

• An AWS account with an IAM user or role that has S3 access
• The bucket name and region

Required IAM Permissions

At minimum, your IAM user needs the following S3 permissions. You can use the managed AmazonS3FullAccess policy or create a custom policy:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "s3:GetObject",
        "s3:PutObject",
        "s3:DeleteObject",
        "s3:ListBucket",
        "s3:GetBucketLocation"
      ],
      "Resource": [
        "arn:aws:s3:::your-bucket-name",
        "arn:aws:s3:::your-bucket-name/*"
      ]
    }
  ]
}

Setup

Supported Features

S3-Compatible Storage

MigrationFox works with any S3-compatible storage by specifying a custom endpoint:

SFTP / FTP

Migrate files to or from remote servers using SFTP (SSH File Transfer Protocol) or FTP.

Prerequisites

• SSH access to the server (for SFTP) or FTP credentials
• The user account must have read access (source) or write access (destination) to the target directory

Setup

sftp username@your-server.com

sftp -i /path/to/key.pem username@your-server.com

Supported Features

Dropbox

Migrate files and folders to or from Dropbox, including personal and business accounts.

Prerequisites

• A Dropbox developer app
• For business accounts: Dropbox Business admin access

Required Scopes

Setup

Supported Features

Box

Migrate files, folders, and collaborations to or from Box.

Prerequisites

• A Box developer app (Custom App)
• For enterprise access: Box Admin authorization

Setup

Supported Features

SMB / Windows File Shares

Migrate files from on-premises Windows file servers and network shares (UNC paths) using the MigrationFox Windows Agent.

Prerequisites

• A Windows machine with network access to the file share
• Administrator privileges on the machine (for running the agent)
• An active MigrationFox project with an agent token

How It Works

Unlike cloud-to-cloud migrations, on-premises file shares are not accessible from the internet. The MigrationFox Windows Agent runs on a machine inside your network, connects outbound to MigrationFox, and handles local file access securely.

Setup

migrationfox-agent.exe --token YOUR_AGENT_TOKEN

\\fileserver\shared\documents

Supported Features

Discovery / Scanning

Before migrating any data, MigrationFox scans your source environment to build a complete inventory. This process is called discovery.

Running a Discovery Scan

1. In your project, ensure the source connection is configured and authenticated
2. Click Start Discovery (or create a discovery job via the API)
3. MigrationFox will recursively scan all files, folders, and metadata
4. The scan typically takes a few minutes for small sources, up to several hours for millions of files

Discovery Report

After scanning completes, the discovery report shows:

• Total file count and total size
• Folder tree with nested file counts and sizes
• File type breakdown — e.g., 40% Documents, 30% Images, 20% Videos
• Large files over 100 MB (flagged for monitoring)
• Permission summary — who has access to what
• Duplicate detection — files with identical content hashes

Selective Migration

After discovery, you can choose to migrate everything or select specific folders. This is useful for phased migrations or excluding irrelevant content.

Provisioning

Provisioning creates the destination structure before migrating data. This ensures all target containers (sites, libraries, drives, folders) exist before files are transferred.

What Gets Provisioned

How to Use

1. Run Discovery on the source first
2. Review the folder structure in the discovery report
3. Configure any folder mappings if you want to remap paths
4. Click Provision Destination to create the structure
5. Once provisioning completes, start the migration

Migration Modes

MigrationFox supports three migration modes that determine how files are handled during transfer.

Folder Mapping

Folder mapping lets you remap source paths to different destination paths during migration. This is useful when the destination has a different organizational structure.

How It Works

You define mapping rules that transform source paths into destination paths:

Source Path                    →  Destination Path
/Marketing/2024/Campaigns     →  /Departments/Marketing/Campaigns-2024
/Engineering/Docs             →  /Technical/Documentation
/Shared/Photos                →  /Media Library/Photos

Mapping Rules

• Exact match — Map a specific folder to a specific destination
• Prefix match — Map all content under a source prefix to a destination prefix
• Flatten — Move all files from nested subfolders into a single destination folder
• Skip — Exclude specific folders from migration entirely

Conflict Resolution

When a file already exists at the destination with the same name, MigrationFox uses the conflict resolution strategy you've configured.

Permission Migration

MigrationFox can migrate file and folder permissions (sharing settings) from the source platform to the destination platform.

How Permissions Are Mapped

Permissions are mapped by email address. If a user has access to a file on the source (e.g., Google Drive sharing), MigrationFox will grant the same user access at the destination (e.g., SharePoint permissions), provided the user exists in the destination directory.

Permission Mapping Matrix

Bandwidth Throttling

Control the transfer speed to avoid saturating your network or hitting API rate limits.

Configuration

In your project settings, you can configure:

• Maximum bandwidth (MB/s) — Limits the total transfer speed
• Concurrency — Number of files transferred in parallel (default: 4)
• Schedule windows — Run migrations only during specific hours (e.g., nights/weekends)

Recommendations

Scheduling

Schedule migration jobs to run at specific times. This is useful for running migrations during off-peak hours or for recurring delta syncs.

How to Schedule

When creating or editing a migration job, set the Scheduled Start time. The job will be queued and will start automatically at the specified time.

Scheduling Options

• One-time schedule — Run once at a specific date and time
• Recurring schedule — Run on a schedule (e.g., daily at 2 AM for delta syncs)
• Immediate — Start the job right away (default)

{
  "jobType": "MIGRATION",
  "mode": "DELTA",
  "scheduledAt": "2026-03-25T02:00:00Z"
}

API Reference

MigrationFox provides a REST API for programmatic access to all migration features. Full API documentation is coming soon.

Authentication

All API requests require a Bearer token. Generate an API key from Settings → API Keys in the MigrationFox dashboard.

curl -H "Authorization: Bearer YOUR_API_KEY" \
  https://api.migrationfox.com/v1/projects

Base URL

https://api.migrationfox.com/v1

Endpoints (Preview)

Webhooks

Configure webhooks to receive real-time notifications about migration events.

Supported Events

Configuration

In your project settings, go to Webhooks → Add Webhook. Provide:

• URL — Your endpoint that will receive POST requests
• Events — Which events to subscribe to
• Secret (optional) — Used to sign payloads for verification

Payload Example

{
  "event": "job.completed",
  "timestamp": "2026-03-24T15:30:00Z",
  "data": {
    "jobId": "job_abc123",
    "projectId": "proj_xyz789",
    "status": "COMPLETED",
    "filesTransferred": 15420,
    "bytesTransferred": 52428800000,
    "duration": 3600,
    "errors": 3
  }
}

Troubleshooting

Common errors and their solutions.

Still Need Help?

If your issue isn't listed above:

• Check the job details page for per-file error messages
• Review the audit log for detailed operation history
• Contact support at support@migrationfox.com

Security

MigrationFox is designed with security at every layer. Here's how your data and credentials are protected.

Data Handling Summary