Migrate from Blue Link ERP to Microsoft Dynamics 365 Business Central

Blue Link Customer records map to Dynamics 365 Customer (Customer table) with contact details, multi-currency settings, and credit status preserved. Blue Link's per-customer currency flag maps to Dynamics Customer Currency Code and the associated Currency table. We validate that the destination currency codes in Dynamics match the Blue Link source before Customer insert. Any Customer without a valid currency mapping is held in the reconciliation queue.

Blue Link Vendor records map to Dynamics 365 Vendor with address, payment terms, and multi-currency flags preserved. Vendor-to-PO linkage is re-established after Purchase Order migration. We validate that each Blue Link vendor's payment terms code exists in Dynamics or create the corresponding Payment Terms record during the vendor migration phase.

Blue Link inventory items with multiple UOM variants per SKU require consolidation strategy during migration scoping. If Dynamics 365 supports native multi-UOM per item (available in Business Central), we preserve the full set as Item Unit of Measure records. If the destination does not support native multi-UOM at the customer's tier, we consolidate to a primary SKU and flag secondary UOM records in the migration runbook for manual re-entry. We also map Blue Link reorder points to Dynamics Item Reorder Point records scoped per Location.

Open Sales Orders migrate as the final migration phase, extracted just before Go-Live to minimize fulfillment gaps. We extract order headers and line items, map the Blue Link sales header status to Dynamics Sales Status, and flag any partial-shipment orders requiring line-level status carry-forward. Customer and item lookups are resolved before order insert. We run a delta validation check within 24 hours of Go-Live to capture any orders placed in the extraction-cutover window.

Open Purchase Orders map to Dynamics Purchase Orders with vendor linkage validated before insert. PO-to-receipt linkage does not carry forward automatically; we document each open PO receipt status in the migration runbook so the customer's receiving team can reconcile open receipts against the new Dynamics PO lines. Line items map with item number, quantity, and unit cost preserved.

Blue Link lot numbers migrate to Dynamics Item Tracking records linked to Item Ledger Entries. Lot assignment at the shipment line level is preserved as Item Tracking Detail records. For pharmaceutical and food distributors, lot traceability is a compliance requirement; we ensure the lot tracking code in Dynamics is configured to match the lot number format from Blue Link before any inventory transactions are posted.

Blue Link AP records (vendor invoices, payment terms, cash requirements) map to Dynamics Vendor Ledger Entries. Unpaid and partially paid invoices are flagged for status reconciliation at cutover. We map Blue Link payment terms to Dynamics Payment Terms codes, and any outstanding checks or scheduled payments are documented as open payables requiring manual resolution in the destination.

Blue Link AR records (invoices, collections tracking, credit checks, cash application) map to Dynamics Customer Ledger Entries. Collections history does not migrate as an activity log; we carry forward the outstanding invoice balance and document the open invoice list for the customer's AR team to reconcile. Credit limit values migrate to Dynamics Customer Credit Limit fields.

Blue Link's full Chart of Accounts hierarchy maps to Dynamics G/L Account records. Custom segments or departmental cost centers in Blue Link map to Dynamics Dimensions (Global Dimension 1 and 2, plus custom-defined Analysis Dimensions). Any Blue Link account numbers that conflict with the destination account number format are flagged during the data audit and resolved before Account migration. Account type mapping (Asset, Liability, Income, Expense) carries forward from Blue Link's account classification.

Blue Link multi-warehouse configurations and bin-level tracking map to Dynamics Location records. Bin-level assignments in Blue Link that exceed the destination's bin configuration capability are flagged in the runbook for manual reconfiguration after Go-Live. We map the Blue Link warehouse code to the Dynamics Location Code as the primary identifier.

Blue Link stores document attachments at the record level in a proprietary format not accessible via documented export endpoints. We do not migrate document attachments as binary data. We flag every record-level attachment during the data audit, document each one in the migration runbook with its source record reference, and advise the customer to use Blue Link's built-in export or support-assisted extraction for binary files. Post-migration, the customer re-uploads documents to SharePoint or Dataverse and links them to the migrated records.

Blue Link's native integrations with Amazon, eBay, and Shopify pull channel orders into the system with platform metadata. Historical eCommerce orders in Blue Link migrate as standard Sales Orders with a custom Channel Source field set to Amazon, eBay, or Shopify. The channel linkage itself does not carry forward because Business Central does not have native bundled eCommerce connectors. We document the reconnection steps for each channel as a separate configuration task for the customer's admin team.