Migrate from MERCI to Microsoft Dynamics 365 Business Central

MERCI Customer records with address, contact, and lifecycle data map to Dynamics 365 Business Central Contact (for CRM-driven workflows) or Customer record (for Finance-ledger posting). We flatten MERCI's billing and shipping address sub-records into the destination address fields. Where MERCI uses custom customer classification codes, we map them to a Customer Posting Group or Customer Group in Dynamics 365. Customer payment terms migrate to Business Central Payment Terms and Finance Customer groups. The MERCI customer_id becomes a custom source_id__c field for reconciliation.

MERCI Sales Orders carry order headers and line items in separate database rows linked by foreign key. We split these into Dynamics 365 Business Central Sales Header (Document Type = Order) and Sales Line records, with the MERCI order_id preserved as a custom order_no__c field. Order dates and expiration logic migrate to Ship Date and Finish Date fields. Line item references to MERCI Item are resolved to Business Central Item No. via the item mapping before insert to satisfy the foreign-key constraint. Partial failures on individual lines do not block the entire order; we log line-level errors separately.

MERCI Invoices reference parent Orders and carry payment terms, tax codes, and line items. We map Invoice headers to Business Central Sales Invoice Header and line items to Sales Invoice Line, preserving the order-to-invoice linkage by embedding the source order_id as a custom field. Open versus closed invoice status requires mapping to the corresponding Business Central Posted or Unposted document type. If MERCI stores invoices as closed records only (no draft state), we post them directly in Dynamics 365. Tax codes are verified against the destination Tax Setup before migration.

MERCI Items include product and service variants with pricing tiers, cost methods, and unit of measure. We map Item master records to Business Central Item with Type (Inventory vs. Service vs. Non-Inventory), Costing Method (FIFO, Average, Standard), and Reorder Policy preserved. Bundle and kit compositions in MERCI must be expanded into their constituent BOM components and mapped to Business Central Assembly Lists or Production BOMs. Pricing schedules map to Business Central Price Lists with Customer Price Groups resolved at migration time.

MERCI Chart of Accounts with account codes and names maps directly to Dynamics 365 G/L Account. Account types (asset, liability, equity, revenue, expense) must be verified against the destination account type taxonomy, as MERCI uses a simplified five-type classification that may not align with the more granular Dynamics 365 account category structure (Posting, Heading, Total, Begin-Total, End-Total). We preserve MERCI account codes as Account No. and add a custom source_account_code__c for audit. If the customer uses dimensional reporting (Cost Center, Department), we configure Account Categories and Default Dimensions before migration.

MERCI Vendor records parallel Customer records in structure. We map vendor contacts, payment terms, and bank account details to Dynamics 365 Vendor using the same address-flattening logic applied to customers. Vendor-specific fields such as Vendor Posting Group (determines how payables are posted to the G/L), and Remit-To addresses migrate to Business Central Vendor or Finance Vendor records. PAYMENT TERMS and shipment methods are resolved to the corresponding Dynamics 365 Payment Terms and Shipping Agent codes.

MERCI Employee records carry department, job title, and compensation fields. We map these to Dynamics 365 Business Central Employee objects with the relevant demographic and employment data fields. Any effective-dated compensation history in MERCI is preserved in custom EffectiveDate and CompensationAmount fields on the Employee record or in a related Compensation History custom entity. If the destination uses Human Resources module, we map Employees to the HR module Employee table with Job Title, Department, and Employment Date preserved.

MERCI Vendor Invoices map to Business Central Purchase Header (Document Type = Invoice) and Purchase Line records. The vendor_id foreign key is resolved to the destination Vendor No. before insert. Tax amounts and GL account assignments for each line are verified against the destination posting group setup. If MERCI stores only posted vendor invoices, we import them as posted purchase invoices rather than draft invoices.

MERCI Purchase Orders map to Business Central Purchase Header (Document Type = Order) and Purchase Line records. We preserve the MERCI purchase_order_id as a custom po_no__c field and resolve Item and Vendor references via the item and vendor mapping. Status migration maps MERCI PO statuses (open, closed, received) to Business Central Release Status and Receipt status fields.

MERCI inventory quantities and warehouse locations map to Business Central Item Ledger Entries and Warehouse Entries. We compute the opening inventory balances as of the migration cutover date and post them as Positive Adjustment entries with a migration-specific reason code. Inventory valuation method (FIFO, Average, Standard) is pulled from the MERCI Item record and must match the Business Central Item Costing Method setting before stock data inserts.

Historical G/L Entries from MERCI map to Business Central G/L Entry records. This is the highest-risk mapping because G/L Entry numbers in Dynamics 365 are system-assigned and sequential, and closing periods are irreversible. We import historical G/L data with document date, G/L account, description, debit amount, and credit amount preserved, but we defer period closing until the customer admin confirms all entries are reconciled. Netting entries (customer and vendor payments applied to invoices) are reconstructed from MERCI payment application records and posted as Bank Account Ledger Entries or Customer and Vendor Ledger Entries in Dynamics 365.

MERCI stores file attachments (order documents, images, PDFs) in a proprietary blob store with no public export endpoint. Binary attachments cannot be retrieved via API or standard CSV exports. We flag attachment objects as unsupported during scoping and direct customers to download files manually from the MERCI UI or to request a full blob export from their MERCI account manager. If document volumes exceed a practical manual download threshold, we recommend a direct database dump from the AWS-hosted MERCI instance as a separate project outside the standard migration scope.