Migrate from Agility ERP to Microsoft Dynamics 365 Business Central

Agility ERP Customer records map directly to Dynamics 365 Customer (which is a party-type entity that covers both people and organizations). Address, contact name, phone, email, and payment terms transfer as standard fields. We validate email format and flag duplicate customers by name and tax ID before import. Dynamics 365 requires a Customer template (Customer Template field) to be set during import; we pre-create template assignments during the discovery phase.

Vendor records including remit-to addresses, tax IDs, and payment terms move 1:1 to Dynamics 365 Vendor. We check for duplicate vendor names across the import set to prevent double-creation. Remit-to address mapping aligns with Dynamics 365's separate Remit-to Address concept, which Agility ERP may store as a sub-address on the vendor record.

Open sales orders transfer with line items, quantities remaining, order date, and customer reference. Status mapping is required: Agility ERP's proprietary statuses (Open, Released, Backordered, Pending) must translate to Microsoft Dynamics 365 Sales Order status values (Open, Released, Shipped, Invoiced). We build a customer-specific status lookup table during discovery. Header-level discount and freight fields map to Dynamics 365's respective posting group and charge amount fields.

Open purchase orders transfer with the same status-mapping logic applied to sales orders. Supplier reference fields, expected receipt dates, and line-level purchase quantities migrate with the parent Purchase Order record. We preserve the original Agility ERP purchase order number in the External Document Number field for audit trail continuity.

Inventory items carry cost layer data (average cost, FIFO layer, or lot cost) that requires explicit mapping to the destination's costing method. Agility ERP average cost maps to Dynamics 365 Standard Cost; Agility ERP FIFO maps to Dynamics 365 FIFO; Agility ERP lot cost maps to Dynamics 365 Specific. Stock on hand and reorder point values transfer but reorder points require re-evaluation against Dynamics 365's replenishment system. Unit of measure conversions are preserved as UOM schedules in Dynamics 365.

Account codes, descriptions, and classification (Asset, Liability, Expense, Revenue) move across. Agility ERP account codes that exceed Dynamics 365's character limit (typically 20 characters in Business Central) are flagged and renumbered during scoping, and we deliver a GL code mapping table alongside the migrated chart of accounts. Account type mapping (Posting vs. Heading vs. Total) aligns with Dynamics 365's account category structure.

Agility ERP does not expose fixed asset records through its standard reporting or API layer. We flag any customer with a non-zero fixed asset balance during scoping and coordinate a direct database extract with Agility ERP support before the migration window. This is a high-severity gotcha: the extract requires a separate professional services engagement on the Agility side and adds lead time of two to four weeks. Depreciation schedules, asset books, and acquisition dates migrate to Dynamics 365 Fixed Asset setup once the extract is received and validated.

Historical journal entries transfer as General Journal lines with memo, date, and amount. We flag entries that contain embedded account IDs from the legacy chart of accounts and remap them to the new Dynamics 365 GL structure before loading. Only open or recent period entries are typically migrated; fully closed and reconciled periods are archived per the customer's period-close policy.

Agility ERP stores custom fields in a non-standard extension table outside the main API layer. Each custom field requires field-by-field review to identify its data type, then explicit creation of the equivalent custom field in Dynamics 365 before import. We do not attempt automated custom field migration without this review, because mis-typed custom fields cause import failures at record level. The customer receives a custom field inventory listing every extension field with recommended Dynamics 365 field type.

Warehouse and location codes from Agility ERP map to Dynamics 365 Locations (or Sites in Finance & Operations). Bin and shelf address structures transfer where present. Location-specific inventory quantities require separate inventory posting group assignment in Dynamics 365 during import to maintain accurate on-hand reporting per site.

Payment terms (Net 30, Net 60, 2/10 Net 30, etc.) map to Dynamics 365 Payment Terms templates. We create Payment Terms records in Dynamics 365 during configuration using the same discount percentages and due date calculations as the source system. Terms that do not have a direct Dynamics 365 equivalent are flagged for the customer's finance team to validate.

Agility ERP tax codes map to Dynamics 365 Tax Group definitions with associated Tax Product Posting Group assignments. We audit the source tax jurisdiction list against Dynamics 365's available tax posting profiles and flag any jurisdiction that requires a new VAT or sales tax posting group setup before import begins.

UOM codes and conversion factors from Agility ERP transfer to Dynamics 365 UOM schedules. We validate conversion ratios against Dynamics 365's UOM precision requirements and flag any conversion that would lose precision at the destination.