Business Central tenant migration without losing data or access
A Business Central tenant migration moves your environments to a new Microsoft Entra tenant. It often follows a merger, a split or a Microsoft 365 consolidation. We plan the route and prepare licenses and users in the destination. Then we move the data and reconnect every link. Finally, we reconcile the result, so people sign in to the same company they left.
Last updated
When a Business Central tenant migration is needed
Each Business Central online setup sits in one Microsoft Entra tenant. It is the same directory that holds your Microsoft 365 users. When that directory changes, Business Central has to follow. Acquisitions are the usual cause. The buyer wants the acquired company's users, mail and ERP in its own tenant. It also wants its own security rules.
The opposite case is a divestiture. One company must leave a shared environment and continue in a tenant of its own. Other triggers include a trial that quietly became production. Another is a group that merges several Microsoft 365 tenants into one. Each case needs a different route.
Explain your tenant situation →
- ✓Merger or acquisition
- ✓Divestiture of one company
- ✓Microsoft 365 tenant consolidation
- ✓Trial tenant used as production
- ✓Group restructuring
Choosing the route for a Business Central tenant migration
When a whole setup is moving, Microsoft supports a transfer between tenants. You do it in the Business Central admin center. An admin on the source side starts the transfer. An admin on the destination side accepts it. Companies, data and extensions move in one step.
Sometimes only part of an environment is moving, such as one company out of five. Then a transfer is too blunt. So we create a fresh environment in the destination tenant. Next, we bring across setup, master data, open documents and balances. We use packages or APIs. Also, we can keep history in a read-only copy for reference.
Compare migration routes together →- ✓Whole environment transfer
- ✓Single company data move
- ✓Fresh start with balances
- ✓Read-only copy for history
- ✓Sandbox rehearsal first
Users, licenses and permissions in the new tenant
Data moves, but identities do not. A user in the destination tenant is a different account, even when the person and the name are the same. You must buy and assign licenses in the destination before anyone can sign in. Each new account also needs its permission sets and user groups again.
We export the current users and their permissions. We also export role centers and any personal settings worth keeping. Then we rebuild that picture in the new tenant. Places where setup stores a user ID need attention too. Examples are approval users, salesperson links, warehouse staff and job queue entries that run under a named account.
Plan the user switch →- ✓Licenses assigned in destination
- ✓Permission sets reapplied
- ✓Approval users remapped
- ✓Warehouse employees updated
- ✓Job queue owners reset
Extensions and integrations after the tenant changes
Anything that signs in against the tenant breaks when the tenant changes. API links use an app registration in Microsoft Entra ID. So they need a new registration and new consent. Power BI reports, Power Automate flows, the Outlook add-in, the Shopify connector and bank feeds all need a new target.
Extensions need a check of their own. Publishers license marketplace apps, often by tenant ID. So each publisher must hear about the move. Per-tenant extensions travel along with a transfer. In a freshly built one, you must publish them again.
List your integrations with us →- ✓Entra app registrations
- ✓Power BI datasets and reports
- ✓Power Automate connections
- ✓Marketplace app licenses
- ✓Bank and payment links
How we run a Business Central tenant migration
First, we take an inventory. It covers environments, companies, data size, add-ons, links, users and licenses. From that, we write a runbook. Then we rehearse the move with a sandbox copy. So we know the timings and surprises in advance. Last, we schedule the production move outside working hours, with both tenant admins on the call.
Afterwards, we reconcile. We compare the trial balance, open receivables and payables, stock value and record counts. We do it for every company, from source to destination. The common pitfalls are forgotten integrations, late license orders and an update window that collides with the move. You get the runbook, the match results and the list of reconnected services.
Schedule a migration plan →- ✓Environment and integration inventory
- ✓Rehearsed move runbook
- ✓Reconciliation per company
- ✓User and permission map
- ✓Post-move test results
Business Central tenant migration questions
Can a Business Central tenant migration move an environment?
Yes. Microsoft offers a transfer step in the Business Central admin center. An admin on the source side starts it, and an admin on the other side accepts it. It arrives with its companies, data and extensions. You must set up users, licenses and integrations again. We list each one in the runbook. We also test sign-in for a pilot group before the full move. So the first morning after cutover is calm, and people open the same company they used the day before.
Will transaction history survive a Business Central tenant migration?
With an environment transfer, yes, because the whole database moves. When we split out one company, we normally bring balances and open documents. We keep the full history in a read-only copy for lookups and audits. So nobody loses sight of old invoices, payments or stock movements. You can also decide with us how long to keep that copy before you retire it. We write that choice into the runbook. Auditors then know where to look. Staff know where to find an old invoice.
Do users keep their passwords and settings?
Users sign in with their account in the destination tenant. So credentials follow that tenant's rules. Permissions and personal settings belong to the old accounts. You must apply them again. We prepare that in advance from an export of the current setup.
Is a tenant migration the same as a cloud migration?
No. A cloud migration moves data into Business Central online. It comes from on-premises Business Central, NAV or Dynamics GP. It uses Microsoft's cloud migration tool. A Business Central tenant migration moves a setup that is already online. It goes from one Microsoft Entra tenant to another.
What needs to be ready in the destination tenant?
First, licenses: assign Business Central licenses to the users who will sign in. Next, an admin who can accept the transfer. Then a free environment slot and enough storage. Finally, the app registrations and service accounts your links will use after the move.
Book a discovery call
Let's talk through your move to Business Central.
A focused call with a senior consultant. We learn how your business runs today, give you an honest view on whether Business Central fits, and outline scope and next steps before you commit to anything.
What happens after you send the form