FEATURE · April 2, 2026 · 5 min read

Automate SharePoint Site Provisioning for Migrations

Before you can migrate files to SharePoint, the destination sites and document libraries need to exist. Manually creating dozens of SharePoint sites, Teams, or Google Drive shared drives is tedious and error-prone. MigrationFox includes built-in provisioning to automate this.

The Problem: Manual Setup Before Migration

A typical migration project looks like this:

Client has 20 departments on Google Drive
Each department needs a SharePoint site with a Documents library
Admin manually creates 20 sites in SharePoint Admin Center
Admin manually creates document libraries in each site
Then starts the actual migration

Steps 3 and 4 alone can take hours. With MigrationFox provisioning, it takes minutes.

What You Can Provision

MigrationFox's provisioning engine supports creating:

SharePoint sites — communication sites or team sites
Document libraries — within existing SharePoint sites
Folders — nested folder structures in any library
Microsoft Teams — with channels (auto-creates the backing SharePoint site)
Teams channels — standard or private channels within existing teams
Google Shared Drives — create shared drives with a specific name
S3 buckets — create AWS S3 buckets for cloud storage destinations

How It Works

From the Project Dashboard

Inside any MigrationFox project, click the Provisioning tool. Select what you want to create:

Choose the resource type (SharePoint site, Team, Shared Drive, etc.)
Select the credential to use
Enter the name and any options (site template, channel type)
Click Create — MigrationFox calls the platform API to provision it

The provisioned resource appears in your project's resource list for reference.

Inline Provisioning During Migration Setup

Even better — MigrationFox lets you provision directly from the migration wizard. When selecting a destination path, if the folder or library doesn't exist, you can create it on the spot without leaving the wizard.

SharePoint Site Provisioning Details

When creating a SharePoint site, MigrationFox uses the Microsoft Graph API:

Creates a group-connected team site (backed by a Microsoft 365 group)
The site is immediately accessible with a Documents library
Permissions are inherited from the group membership
You can add additional document libraries after creation

Batch Provisioning

For large migration projects, you can provision multiple resources in sequence. Create all your SharePoint sites first, then create document libraries within each, then start your migrations. The entire workflow stays within MigrationFox — no need to switch between admin portals.

Why This Matters

Provisioning is the often-overlooked first step of any migration. Tools that skip it force you to manually prepare the destination, adding hours to your project. MigrationFox treats provisioning as a first-class feature because it's part of the migration workflow.