Skip to main content

Transfer #msdyn365bc environment between Tenant.

Hi Readers,

Moving Environment between tenant is something that some customers and partners are looking for. 

In this article we will discuss about How to Transfer Business Central Environment between Microsoft Tenants.

Create transfer on source tenant.

  • Business Central administration center, select Environments > Environment Transfers.
  • Select Transfer Environments.
  • Select the environment(s) to be transferred, specify the Entra tenant ID of the destination tenant, choose a date and time at which the chosen environment(s) should transfer to the destination, and confirm.
  • An environment transfer must be accepted in the destination Entra tenant within 8 hours of creating the transfer on the source tenant.

Accept transfer on destination tenant.

  • Business Central administration center, select Environments > Transfer Environments.
  • Select Receive Environments.
  • Specify the Entra tenant ID of the source tenant you're accepting an environment transfer from
  • Select the environment(s) for which you want to accept a transfer and confirm.

Cancel a pending transfer from source tenant.

  • Business Central administration center, select Environments > Transfer Environments.
  • Select the pending outgoing transfers which you would like to cancel and confirm.


  • only Internal Administrators can execute and accept Transfer request. 
  • Max time 8 Hours to Accept Request.
  • Downtime period typically 30 Minutes.
  • Localization, Azure region, and type of the environment will remain the same, and can't be changed during this operation.
  • Need to reconfigure some add-ins, external applications, and settings after the tenant-to-tenant migration.
  • External integrations may have to be updated.
  • User personalization's will be lost.

Demo Video:

Let me know your views in comment to this article.

Saurav Dhyani


Popular posts from this blog

VIEW SERVER STATE permission on SQL Server?

Hi all, Sometime While trying to Login into a database we face an error message as shown below. --------------------------- Microsoft Dynamics NAV Classic --------------------------- You cannot start Microsoft Dynamics NAV Classic because you do not have the VIEW SERVER STATE permission on SQL Server. Contact your system administrator. --------------------------- OK    ---------------------------

NAV 2013 R2 - Cumulative update 12 Released.

Hi all, Please find below the details of  Cumulative Update 12 released for Microsoft Dynamics NAV 2013 R2. Title - Cumulative Update 12 for Microsoft Dynamics NAV 2013 R2 Build No. - 38053 Release Date - October, 2014 Local Version Included - AU, AT, BE, CH, DE, DK, ES, FI, FR, IS, IT, NA, NL, NO, NZ, SE, UK, RU Download Link Note: Implementing this cumulative update will require a database conversion unless you have already implemented update rollup 5.

NAV 2013 Upgrade Part III - Data Upgrading.

Hi all, As per agenda we need to discuss the data upgrade in NAV 2013. The process is similar to what used to be till NAV 2009 R2 but with some changes. Let's start the process. Remember -  1) You can only upgrade a database to NAV 2013 from NAV 2009 SP1 / R2 SQL Only. 2) The Synchronization of users with SQL Server is no more required.