videoIntegration & APIsofficial - Microsoftreviewed - checked by Opus

What's New: Migrate Record Links and Notes (2025 release wave 2)

Migrating record links and notes from an on-premises database to Business Central online as part of cloud migration (2025 release wave 2). Covers the buffer table, the Migrate record links and notes action on the cloud migration management page, the warnings field, and the required order: replication, then migration, then user mapping.

  1. 0:00 What are record links and notes
  2. 0:29 The problem and solution
  3. 0:53 Cloud migration setup and buffer table
  4. 1:15 Demo: migrating record links and notes
  5. 2:06 Best practices and safety considerations
video Microsoft Dynamics 365 Business Central (YouTube) · 2025-10-01Watch on YouTube

Overview

Record links and notes can hold customer insights, annotations and references. Previously they were not migrated from the on-premises database to the cloud, so partners had to bring them over manually. Now their migration is part of the cloud migration process.

Replication puts the record links and notes into a buffer table so existing records in the cloud are not overwritten. After replication finishes, a user runs the migrate action on the cloud migration management page to move them from the buffer table to the actual table. A new warnings field shows when the record link table has not been migrated since the last replication. The demo shows the full flow.

Key points

  • Record links and notes migration is now part of the cloud migration process. Before, partners spent a lot of time and effort bringing them over themselves.
  • Replication moves record links and notes into a buffer table first, so existing records in the cloud are not overwritten.
  • Run the Migrate record links and notes action on the cloud migration management page after data replication completes. It moves the records from the buffer table to the actual table.
  • Run the migration before user mapping, because user mapping changes the users on the record links and notes to the ones you map to.
  • A new warnings field on the cloud migration management page flags that the record link table has not been migrated since the last replication. The warning clears after the action runs.
  • The presenter says the action does not overwrite existing record links and notes, so it is safe to run and can be run multiple times.

Features

Every feature below: status not stated, demoed.

Feature At
Record links and notes migration 0:40
Cloud migration management page 0:53
Migrate record links and notes action 1:15
Warnings field for record link migration 1:26

AL objects mentioned

As heard in the captions. A name that matches one object page by exact type and name links to it; the others stay as named.

  • page “cloud migration management page” at 0:53

Not found in BC28-30: page “cloud migration management page”.

Quotes

  • 0:17 “record links and nodes are very critical. Uh they can contain customer insights, annotations or references and they are important for your day-to-day decisions”
  • 0:29 “Previously record links and not notes were not migrated from on-rem database to cloud. Uh so partners would have to spend a lot of”
  • 0:40 “But now with new capabilities record links and nodes migration is part of the cloud migration process.”
  • 1:05 “Replications will bring bring the uh record links and nodes to a buffer table so that we don’t override your existing record links and”
  • 2:06 “Make sure you run the record links and notes migration after the replication so that records are moved to the buffer table beforehand.”
  • 2:21 “Also, make sure you do this uh before doing the uh user mapping because when you do the user mapping uh we’ll change the”
  • 2:34 “we do not overwrite your existing record links and notes. So it’s very safe to use. You can run it the run the action”

Presenters (as heard): Onet.