Migrate from Sage 200cloud to Microsoft Dynamics 365 Business Central

Sage 200cloud Departments are a top-level dimension in the chart of accounts and must be loaded before any Nominal Account that references them. We create matching Financial Dimension values in Dynamics 365 Finance and Supply Chain (or Business Central with dimension sets) and map the Sage Department code to the dimension value. Departments do not exist as standalone entities in Dynamics 365 general ledger; they are dimension values applied to account entries. We set up the dimension via the Dimensions page in the General ledger module before any account posting begins.

Sage 200cloud Cost Centres are a second-level analytical dimension similar to Departments. We create a separate Financial Dimension in Dynamics 365 (e.g., CostCentre or BusinessUnit) and map Sage Cost Centre codes to dimension values. Like Departments, Cost Centres are not standalone ledgers in Dynamics 365; they are dimension tags applied to journal lines. We configure the dimension structure in the Chart of Elements before opening balances are posted.

Sage 200cloud Nominal Accounts map directly to Dynamics 365 Main Accounts (also called G/L Accounts). The Sage nominal code (typically numeric, e.g., 1000, 2100) maps to the Main Account number in Dynamics 365, and the account description maps to the Name field. We enable the relevant Financial Dimensions on each Main Account so that the Sage Department and Cost Centre analysis becomes a dimensional tag in Dynamics 365 rather than a structural account code. This is a structural change from Sage's flat nominal code to Dynamics 365's dimensional general ledger and requires careful mapping of Sage's analytical codes to Dynamics 365 dimension values.

Sage 200cloud Customer records combine company details, primary contact, billing address, and credit terms in a single record. Dynamics 365 separates these into Account (the company and billing/shipping data) and Contact (the person-level communication data with the Account as a lookup). We split the Sage Customer into an Account with the customer name and address, and one primary Contact with the contact person's details. The Sage Customer Email field (subject to a 215-character truncation risk per Known Issue 8225) is mapped to the Contact's Email field in Dynamics 365; we flag any source email exceeding 215 characters before insert.

Sage 200cloud Supplier records map to Dynamics 365 Vendor Accounts. We preserve the supplier name, address, payment terms, bank details, and the nominal code assignment from the Sage supplier. Dynamics 365 Vendor Accounts use posting profiles to map to the correct purchase ledger nominal accounts, which we configure during the setup phase. Any Sage supplier with multiple contact persons creates multiple Contact records linked to the same Vendor Account.

Sage 200cloud Sales Orders (SOP) map to Microsoft Dynamics 365 Sales Orders in Finance and Supply Chain or Business Central. We map the order header (customer reference, order date, currency, payment terms) and line items (item number, quantity, unit price, discount) to the corresponding Dynamics 365 fields. The warehouse code from the Sage SOP line maps to the Dynamics 365 Site and Warehouse dimensions on the sales order line. SOP documents must be imported after Customer and Stock Item records are in place to satisfy foreign-key constraints.

Sage 200cloud Purchase Orders (POP) map to Dynamics 365 Purchase Orders. We preserve the vendor reference, order date, and line items. The Confirm Goods Received status from Sage POP is not carried as a field; we map it to the Receipt status in Dynamics 365 purchasing workflow. Purchase Orders are imported after Vendor Account and Stock Item records are established.

Sage 200cloud Product Groups define the top-level stock classification hierarchy. We map Product Groups to Dynamics 365 Product Categories, which are the root-level grouping in the Supply Chain Management or Business Central product catalog. Product Categories serve as the parent of Released Products and drive posting profiles for inventory accounting.

Sage 200cloud Stock Items map to Dynamics 365 Released Products with inventory tracking enabled. The Sage stock item code becomes the Dynamics 365 product number. We enable Site and Warehouse dimensions on the Released Product so that Sage's multi-location warehouse assignments map to Dynamics 365 inventory dimensions. Unit of measure, item weight/dimensions, and default order settings migrate from Sage to the Product's planning and inventory management fast tabs.

Sage 200cloud Stock Opening Balances must be imported after Product Groups and Stock Items are established. We map opening quantity and value to a Dynamics 365 inventory opening journal (or the initial inventory posting in Business Central). The nominal account for the inventory valuation in Sage maps to the inventory ledger account in Dynamics 365, which is configured on the product's storage dimension group. We preserve the physical value and financial value separately for audit reconciliation.

Sage 200cloud Supplier Price Lists map to Dynamics 365 Purchase Trade Agreements or Vendor Price Lines on the Vendor Account. We import the supplier item number, unit price, and lead time as trade agreement lines with an effective-from date matching the Sage price list date. Multiple price breaks per item in Sage map to multiple trade agreement lines with corresponding quantity breakpoints in Dynamics 365.

Sage 200cloud Bank Accounts are nominal records with a bank-account type flag. We map them to Dynamics 365 Bank Accounts in Cash and Bank Management. The bank account number, currency, and opening balance migrate. Bank reconciliation rules from Sage are not carried automatically; we document them for manual reconfiguration in Dynamics 365's bank reconciliation setup.

Sage 200cloud Fixed Assets are tied to Nominal Accounts with acquisition date, depreciation method, and net book value fields. We map them to Dynamics 365 Fixed Assets in Asset Management. The depreciation book and depreciation method (straight-line, reducing balance, etc.) map from Sage's fixed asset depreciation profile to Dynamics 365's depreciation profile. Accumulated depreciation and NBV are carried as opening balance transactions in the Dynamics 365 Fixed Assets ledger. Note that Dynamics 365 Fixed Asset acquisition and depreciation posting profiles must be configured to match the Sage nominal posting setup before asset migration begins.

Sage 200cloud Nominal Budget records are period-level financial budgets tied to nominal accounts and dimensions. We map them to Dynamics 365 Budget Control or Budget Register Entries. Period-level granularity is preserved; Sage's period budget amount becomes a budget register line in the relevant fiscal period. Budget models in Dynamics 365 must be configured before migration to accept the Sage budget data.

Sage 200cloud posted transactions (invoices, credit notes, journal entries) map to Dynamics 365 General Journal lines. We map the Sage account code and dimension assignments to the Dynamics 365 Main Account and dimension values. Transaction dates and voucher numbers are preserved as the journal line date and voucher number. Sage invoice and credit note document references map to the text field on the journal line. Historical transactions are loaded after the chart of accounts, dimensions, and opening balances are confirmed to balance. Fusion5's Dynamics 365 migration research confirms that what appears straightforward in data move often requires restructuring when source and destination schemas differ contextually, so we engage business users early to validate transformed historical data samples before bulk posting.

Sage 200cloud User records and ownership assignments on records (e.g., which user owns a customer or sales order) map to Microsoft Entra ID users in Dynamics 365. We match Sage users by email address to the corresponding Entra ID user, then link to the Dynamics 365 User record. Any Sage owner not present in Entra ID is held in a reconciliation queue for the customer's IT admin to provision before the migration resumes. User-role assignments in Sage map to Security Roles in Dynamics 365, which we document separately for admin configuration.