Jobs That Survive Restarts
Every job's progress is saved as it runs. If the app closes unexpectedly, open it again and it picks up automatically — no starting over.
TenantBridge runs every workload from your own machine, keeps jobs on track through interruptions, and gives you a clear view from start to finish.
Run multi-day tenant migrations with confidence on infrastructure you choose — workstation, VM, or server. TenantBridge is not a hosted cloud service, and the path from setup through cutover stays predictable.
Every job's progress is saved as it runs. If the app closes unexpectedly, open it again and it picks up automatically — no starting over.
Set up all your site mappings, batches, and options in the Config views. Nothing runs until you switch to Migrate and say so. Intent and execution are always separate.
TenantBridge is a single executable with everything built in — the web UI, the job engine, the database. No Node, no Python, no Docker required.
Set up your Microsoft 365 and Google Workspace connections once. They're saved and reused across every project, and stored encrypted on your machine.
SharePoint sites, shared drives, email, calendar, contacts, and OneDrive — migrate all of them from the same app, managed from the same Migrate view.
Run Discovery to get a real list of SharePoint sites, drives, and mailboxes from the source. Map against verified data, not assumptions.
The web interface is only accessible from the machine running TenantBridge — never exposed to the internet. Credentials are encrypted and never sent to a third party.
Every job writes a full log to your machine as it runs. View a live tail in the app, or open the log file in Explorer for the complete history.
Watch file counts, transfer rates, and errors update in real time. A built-in metrics endpoint is also available for operators who monitor externally.
Map document libraries to Shared Drives, preserve folder structure and permissions, and run transfer jobs directly from your machine.
Batch mailbox migration with parallel workers, date range filters, and a per-message ledger — restarts pick up exactly where they left off.
Full GWS-to-GWS and M365-to-GWS tenant moves — email, Drive, Calendar, Contacts, and SharePoint from a single unified Migrate view.
A consistent, predictable path from first setup to jobs running — no surprises mid-project.
Enter your Microsoft 365 and Google Workspace credentials once. Connectors are saved globally and reused across every project — no re-entering credentials for each migration.
A project ties together your source and destination. Set domain name rules for cross-tenant moves. Projects can be archived when complete and reopened if you need to revisit them.
Run Discovery to pull the list of SharePoint sites, drives, and mailboxes from the source tenant. Everything is saved as a snapshot so you're mapping against real data — not guesswork.
Map each SharePoint site or shared drive to its destination. Choose whether to create a new destination drive or map to an existing one. Set up mailbox batches and per-module options. This is all configuration — nothing runs yet.
Switch to Migrate and see every job in one table — files, email, calendar, contacts, and OneDrive. Hit Start All or start individual jobs. Live progress, current file, and errors update in real time.
If the app closes mid-run — or your machine restarts — job state is already saved. Open TenantBridge again and it reconciles any interrupted work automatically. Long transfers also handle credential refreshes on their own.
TenantBridge is built for operators who need to know exactly where their data is at every step.
The web interface listens on your local machine only — it can't be reached from outside your computer. There's no cloud relay, no remote access, no inbound port to secure.
Your Microsoft and Google API credentials are encrypted before being saved. They're never included in exports or visible through the app — only used in the moment a job needs them.
All job state and mappings are stored in a local database file on your machine. Nothing to provision, nothing to maintain, and the database path is always shown in the app.
Every job transition is recorded as it happens. If TenantBridge closes mid-migration, the next launch finds exactly where things were and continues cleanly — no silent failures, no lost progress.
.exe). On macOS and Linux, TenantBridge can be built from source and run from the command line. On those platforms, closing the terminal doesn't stop a running migration — the worker keeps going in the background until you stop it.
Request a demo or reach out — we'll walk you through it.