Migrate from Relic ERP to Microsoft Dynamics 365 Business Central

Relic ERP's flat account structure maps to Dynamics 365's dimensional chart of accounts. We identify every account in Relic ERP, assign the correct Main Account type (Revenue, Expense, Asset, Liability, Equity), and design the financial dimension structure (typically Department, Division, Cost Center, Project) based on how Relic ERP stores segment data. The chart of accounts is deployed to the D365 legal entity via the Data Management Framework before any transactional data loads. Account numbers are preserved as the Main Account value; account names migrate as the Name field.

Relic ERP's fiscal year configuration migrates to D365 Ledger with the same period structure (monthly, quarterly, 4-4-5, or custom). The Ledger is assigned to the legal entity and the fiscal calendar is linked. If Relic ERP uses a non-standard fiscal year (e.g., April-March), this is configured in D365 before opening balances are posted. Period status (Open, Closed, On Hold) is mapped to D365 LedgerPeriodStatus.

Relic ERP Customer records map to D365 Account (organization-level data including billing address, credit limit, payment terms) and optionally to Contact (individual contact points within the account). Customer account number from Relic ERP becomes the D365 Account Number; this field is the dedupe key during import. Payment terms, tax group, and invoice account assignment migrate as Account fields. Any party-role flags (e.g., one-time customer) map to D365 Customer type.

Relic ERP Vendor records map to D365 Vendor (the organization) with Contact records for individual procurement contacts. Vendor account number becomes Vendor Account Number and serves as the dedupe key. Remit-to address, W-9 / tax registration, and payment terms migrate to the Vendor. If Relic ERP stores vendor-specific GL expense accounts, these map to the Vendor's Default Purchase Posting profile.

Relic ERP product and item records map to D365 Released Products with product type (Item, Service, BOM, Planning) determined by the Relic ERP item classification. The item number, item name, and base unit of measure migrate. Product dimensions (Size, Color, Style, Configuration, Site, Warehouse) are created as D365 Product Dimensions based on how Relic ERP stores variant data. Cost price and sales price from Relic ERP migrate as Trade Agreements (price/discount) in D365.

Inventory on-hand quantities in Relic ERP migrate to D365 On-Hand entries keyed by product, site, warehouse, location, and batch/LOT number. Site and warehouse structures from Relic ERP are pre-created in D365 before on-hand data loads. If Relic ERP tracks lot numbers or expiration dates, these migrate as inventory dimension attributes on the on-hand record. The physical inventory adjustment date and count quantity are preserved.

Open Sales Orders from Relic ERP migrate to D365 Sales Order with status Preserved as Open. Order number becomes the D365 Sales Order number; customer account, line items, quantities, prices, and delivery dates migrate. If the D365 on-hand inventory does not yet reflect the open order demand, we flag the reservation discrepancy in the reconciliation report. Completed or invoiced orders do not migrate as open records; historical invoice data migrates separately asPosted Invoice records.

Open Purchase Orders from Relic ERP migrate to D365 Purchase Order with status Preserved as Open. Vendor account, line items, quantities, costs, and delivery dates transfer. D365 purchase order number is assigned at migration time; the original Relic ERP PO number is stored in the External Reference Number field for audit traceability. Confirmed or received purchase orders are migrated as posted packing slips or invoices, not open PO records.

Open and recently posted customer invoices from Relic ERP migrate to D365 Free Text Invoice or Sales Invoice, depending on whether the source uses invoice lines or freeform invoice structure. Historical posted invoices within a configurable retention window (typically 13 months) migrate as read-only Customer Invoice Journal records. Invoices older than the retention window are not migrated; we flag the scope during discovery and recommend exporting a summary ledger report for audit purposes.

Bill of Materials from Relic ERP migrate to D365 BOM (for standard manufacturing) or Formula (for process manufacturing with yield/scrap). BOM lines with component items, quantities per, and operations resources transfer to the D365 BOM Designer. Route definitions migrate to D365 Route if the destination uses production floor control.

Relic ERP employee records used for purchasing approvals or inventory transactions migrate to D365 Human Resources Worker. Worker number, name, employment status, and organizational hierarchy transfer. Worker is linked to the D365 User for system access. If the destination D365 deployment does not include Human Resources, employee references are stored as Contacts with a custom PartyType field.

Relic ERP warehouse and location structures map to D365 Site (top-level), Warehouse (storage unit), and Location (bin/rack) hierarchy. Location address and warehouse parameters (allow mixed items, allow partial picks, etc.) migrate. If Relic ERP uses zone logic, this maps to D365 Warehouse Configuration zones.

Relic ERP tax codes and tax groups migrate to D365 Tax Group (customer/vendor assignment) and Sales Tax Code (rate and posting). Tax jurisdictions from Relic ERP are mapped to D365 Tax Authority records. If Relic ERP stores nexus or tax registration by state/province, this data populates the D365 Tax Registration table on the legal entity.

Relic ERP user-defined fields and custom fields on standard records migrate to D365 extension fields (Field Extension or ISV-added fields). We document each UDF with its data type, field length, and validation rule. D365 extension fields are added to the relevant table and form before migration loads begin. Very-long-text UDFs may require splitting across multiple D365 fields if the platform enforces shorter limits.