{"id":997950,"date":"2025-09-12T12:39:08","date_gmt":"2025-09-12T12:39:08","guid":{"rendered":"https:\/\/ioi.gmbh\/?p=997950"},"modified":"2026-09-02T06:07:10","modified_gmt":"2026-09-02T06:07:10","slug":"business-central-delta-migration-with-datamigrate-pro","status":"publish","type":"post","link":"https:\/\/ioi.gmbh\/en\/2025\/09\/12\/business-central-delta-migration-with-datamigrate-pro\/","title":{"rendered":"Business Central Delta Migration with DataMigrate Pro"},"content":{"rendered":"\n

Records that have been transferred successfully do not have to be transferred to Business Central again \u2013 unless they were changed in the source database in the meantime. Navision provides an additional column named timestamp<\/code> in every table by default. In normal operation it is used to detect changes to records and to display the familiar message “\u2026 Another user has modified the record \u2026”.<\/p>\n\n\n\n

DataMigrate Pro uses this mechanism and determines from the timestamp<\/code> which records have changed since the last transfer.<\/p>\n\n\n\n

All records for which Business Central has confirmed a successful transfer are stored automatically in a log table, together with their timestamp<\/code>.<\/p>\n\n\n\n

A dynamic query makes sure that in the --changesonly 1<\/code> operating mode only those records are transferred again whose current timestamp<\/code> is not yet recorded in the log table. The system also detects records that have already been logged but have since been deleted in the source system \u2013 for example when entries were removed after the migration had started.<\/p>\n\n\n\n

The following command therefore transfers only new or changed master data and setup data to Business Central:<\/p>\n\n\n\n

<\/circle><\/circle><\/circle><\/g><\/svg><\/span>