topic hubAdministration & Setupofficial - Microsoftreviewed - checked by Opus

Migrate from Business Central on-premises

Migration from Business Central on-premises to Business Central online: the cloud migration process and its phases, preparation, setup, data replication, data upgrade, and completion. It answers what to do at each phase and how to configure, run, monitor, and finish a migration.

Path: Administration > Migrate to Business Central online > Migrate from Business Central on-premises · tier official · system administration · narrative reviewed (checked by Opus)

Overview

This section describes how to move a Business Central on-premises solution to Business Central online. The Overview subtopic explains the end-to-end process, its five phases, and the Cloud Migration Management page. It also covers the version 14 reimplementation tool, which is for essential data only.

The other subtopics follow the phases in order. Prepare covers planning, data scope, cleanup, SQL table definition alignment, data size estimates, and performance tuning. Set up cloud migration covers Cloud Migration Setup, the integration runtime and pipelines, table mappings, replication settings, and permission retention. Replicate data explains how replication works and how to run, monitor, pause, or troubleshoot it. Upgrade data covers data upgrade from earlier on-premises versions and skipping the API data upgrade.

The page in this hub, Complete cloud migration, covers the final phase. Start with the Overview to choose an approach, then work through Prepare before configuring anything.

Key points

  • The migration process has five phases and is managed from the Cloud Migration Management page.
  • A version 14 reimplementation tool exists for migrating essential data only.
  • Prepare steps include planning, data scope, cleaning data, aligning SQL table definitions, estimating data size, and tuning performance.
  • Setup involves Cloud Migration Setup, the integration runtime and pipelines, table mappings, replication settings, and permission retention.
  • Replication uses Azure BLOB storage, Azure Data Factory, and change tracking, with separate flows for large and small tables.
  • Replication can be run, monitored, paused, and troubleshot in Cloud Migration Management.
  • Data upgrade applies to earlier on-premises versions, and the API data upgrade can be disabled per company to shorten upgrade time.
  • Completion tasks include migrating record links and notes, disabling cloud migration, running API upgrades, setting up user mappings, reconnecting Sales integration, and monitoring telemetry.

Subtopics

More Learn pages

  • Complete cloud migration: This article describes the task you do to complete the data migration from on-premises to online.

Videos and posts

Linked by a Haiku matcher with a grounding quote from the item’s summary (link/topics.ts); machine-generated.

Source: Microsoft Learn (CC BY 4.0). Descriptions are Learn’s own.

What Learn documents here 8 of 20 Learn pages

Show 12 more