Migration Tabmigrationtab.com
HOW IT WORKS

Discover → map → dry-run → approve → migrate

Every migration domain follows the same cautious rhythm: collect evidence, stage decisions, and only write to Microsoft 365 when an operator signs off.

01Discover

Inventory Forms, Loop, and Bookings with read-only jobs.

02Map

Edit per-line destination mappings before any live write.

03Dry-run

Build the plan and export artifacts without touching M365.

04Approve

Typed confirmation and admin role for mutating operations.

05Migrate

Execute when the evidence ledger says it is safe to move.

WorkstreamApp-only GraphExtra stepOperator action
FormsDelegated OAuth for group formsConnect group Forms in Tenant access
LoopSPE guest grantCopy Set-SPOApplicationPermission scripts
Bookings✓ per business IDManual business IDsPaste IDs when creating discover job
WORKFLOW / STEPS

Five gates before any live write

01

Connect tenants

Register source (and destination) Entra app profiles with encrypted client secrets.

02

Verify prerequisites

Test Graph roles, Forms app/delegated access, and Loop SPE guest grants before running jobs.

Graph app roles Forms app-only Forms delegated Loop SPE grant
03

Discover & export

Inventory Forms, Loop, and Bookings with read-only jobs that produce artifacts and mapping rows.

04

Map destinations

Edit per-line mappings in the console before any live write.

05

Approve live changes

When mutating operations ship, live jobs require typed APPROVE {job-id} confirmation and admin role.

Typed approval required
OUTPUT / ARTIFACTS

Evidence you can hand to auditors

Every discover and export job produces inspectable files in your workspace.