Muokkaa

Jaa

Complete cloud migration to Business Central online

  • Artikkeli

This article explains tasks you do in the final phase of cloud migration—that is, after completing replication, upgrading the data in the online environment, and testing the result of the cloud migration.

Tip

To keep track of which of task you've done, use the Post Migration Checklist page to check off tasks as you go along. To open the checklist, go to Cloud Migration Setup page then select Actions > Setup checklist.

Step 1 Disable the cloud migration

Once you migrate the desired data to Business Central online, you end the migration by disabling cloud migration in the Cloud Migration Setup page. This step is important because each time someone runs the migration, outstanding documents (like for vendors and inventory items) and other changes made in the online target company are overwritten.

When you disable the cloud migration, the cloud migration setup for the environment is deleted. But integration runtime remains. So if you want to migrate data again, you have to first go through the cloud migration setup.

To disable cloud migration, complete the following steps:

  1. Go to the Cloud Migration Management page and select Complete Cloud.
  2. On the Cloud Ready Checklist page, read the information.
  3. If you agree, turn on the I have read and understand the recommended step switch.
  4. Select the Disable Cloud Migration > Yes.

Note

The integration runtime remains installed on your on-premise machine. However, if it's not used for cloud migration within a couple of weeks, its cloud registration is automatically cleaned up. If you want to migrate data again, you must go through the cloud migration setup again and may also need to re-install the Self-hosted Integration Runtime.

Step 2 Run API data upgrade

APPLIES TO: Migration from Business Central on-premises only

This step is only required if you skipped the API data upgrade during the cloud migration. Learn more about skipping API data upgrade.

  1. Sign in to Business Cental online.

  2. Search for and open the Cloud Migration Management page.

  3. Select the Manage API Upgrade action to open the API Upgrade overview page.

    Companies that weren't upgraded have the API Upgrade Status of Disabled.

  4. To run the API data upgrade for a company, do the following steps:

    1. On the API upgrade overview page, select the company name.

      The API Data Upgrade List opens in a new browser tab.

    2. On the API Data Upgrade List page, select all entities, and then select Reset > "Schedule Upgrades > Yes.

      A job queues entry is created and opened.

    3. Schedule the job queue entry to run. Learn more.

  5. Repeat the previous step for each company you want to run the API data upgrade.

You can check the status of job queue entries on the API Upgrade Overview page and restart a job queue entry if it fails. When you restart a job queue entry, it continues at the point where it stopped. It's safe to rerun the job queue entry because it commits and releases any locks and shouldn't cause any performance degradation.

Step 3 Set up users and permissions

User accounts and permissions in Business Central on-premises aren't migrated to the online. To give on-premises users access to the new online tenant, each user needs the following permissions:

  1. An account in the Microsoft 365 tenant with a Business Central license.

    For more information, go to Add users and assign licenses at the same time.

  2. An account in Business Central that's associated with their Microsoft 365 account email and assigned the proper permissions to data in Business Central.

    For more information, go to Create Users According to Licenses.

    Tip

    You can go directly to setting up permission sets from the Cloud Ready Checklist page by selecting Permission Sets.

Step 4 Define user mappings

APPLIES TO: Migration from Business Central on-premises only

If any data or transactions are dependent on a specific on-premises user account, then you must map the on-premises user account to an online user account.

Important

User mappings can only be done once per environment, so it's recommended to do this task as a one of the last step. You can copy to a sandbox and test the changes there so it doesn't affect the production environment.

Map on-premises users to online accounts

  1. Go to the Cloud Migration Management page and select the Define user mappings action.
  2. Use the Define User Mappings page to match on-premises user accounts, shown in the On-premises User field, with online user accounts by filling in the Cloud User field.
  3. When ready, select OK to start the update.

Technical details

  • The users are copied from the on-premises database from both User and User Property tables to the buffer table. If you're using custom SQL scripts to move the data, be sure to include User Property table. If this table isn't included, then no data is copied.
  • Not all tables are included in the rename process. Codeunit 418 User Management is used to rename the records that don't have the table relationship property set. Some tables, like Change Log Entry, aren't supported for this functionality, because they're too large. These tables are excluded from the rename process.

Step 5 Reconfigure the Dynamics 365 Sales connection

APPLIES TO: Migration from Business Central on-premises only

If you're integrating with Dynamics 365 Sales, you have to set up the connection again. For more information, see Integrating with Dynamics 365 Sales.