Migrate from Expand ERP to Microsoft Dynamics 365 Business Central

Expand ERP's Lead Management module maps to either a Dynamics 365 Lead (for unqualified prospects) or Contact (for qualified buyers) depending on the lead's status in the lifecycle. We evaluate the Expand ERP lead status and source fields at migration time, apply a status-threshold rule, and preserve the original lead source and status in custom fields on both Lead and Contact for audit trail and reporting continuity.

Expand ERP Customer records (including billing/shipping addresses, payment terms, and contact details) map directly to Dynamics 365 Customer and Sales documents or directly to an Account record depending on the selected Business Central setup type. Customer currency from Expand ERP maps to the Account's Preferred Currency field, which activates Dynamics 365's multi-currency posting for that customer.

Expand ERP Sales Orders map to Microsoft Dynamics 365 Sales Order documents. The order header (customer reference, order date, delivery date, payment terms) and all line items (item number, quantity, unit price, discount) migrate 1:1 where the destination schema supports them. Open versus closed status maps to the Released or Draft document state in Business Central.

Purchase Orders migrate to Dynamics 365 Purchase Order records. Vendor reference, expected delivery date, and purchase pricing from Expand ERP map directly. Any INR-denominated PO amounts are converted at the cutover exchange rate and stored in the target currency, with the original INR amount preserved in a reference field.

Expand ERP Item master records (product name, SKU, unit of measure, pricing, opening stock) map to Dynamics 365 Item records with inventory posting groups and pricing structures applied. The hs_sku equivalent maps to the Item's No. field. If the migration includes CRM scope, items also generate Product2 records for Opportunity and Quote line item use.

Expand ERP warehouse locations map to Dynamics 365 Location records. Warehouse-level stock balances migrate as opening inventory quantities. Bin or lot serial number tracking is only available if Expand ERP exposes these in its export paths; we request a supplemental inventory report for serialized or batch-tracked items and cross-reference against the standard stock export to fill gaps.

Vendor master data migrates from Expand ERP to Dynamics 365 Vendor records with contact info, address, and payment terms. Vendor currency and payment method map to the Vendor's Preferred Currency and Payment Term fields. Vendor balances from Expand ERP's purchase ledger migrate as open purchase document entries.

Expand ERP POS Billing transactions (transaction ID, date, payment method, line items) are extracted as transaction headers and line items. Dynamics 365 Business Central can receive POS data via Cash Document Journals if the POS module is configured; otherwise we extract POS data as structured transaction records linked to the relevant location and customer. Shift-level settlement reports may require separate export handling since Expand ERP does not always expose register reconciliation data through standard export routes.

Expand ERP Production Jobs (work orders, BOM reference, material consumption, output quantities) map to Dynamics 365 Production Order records. We map the production job header and material consumption lines, though BOM versioning requires field-level review per item family. Output quantities and work center assignments map to the Production Order routing and output journal entries in Dynamics 365.

Expand ERP's export documentation module stores licence numbers, shipping marks, and country-specific customs fields as custom document attributes. These do not map 1:1 to standard Dynamics 365 fields. We extract export document references as structured notes or linked record entities and flag any mandatory customs fields that require manual re-entry at the destination. We preserve the full document attribute set in a JSON blob attached to the related Sales Order or Shipment for audit purposes.

Expand ERP financial account codes and names map to Dynamics 365 G/L Account records. Account type mapping (Asset vs Expense vs Revenue) must be confirmed against the destination's chart of accounts structure during scoping. Sub-account hierarchies and dimension configurations in Dynamics 365 require a pre-migration alignment session with the customer's finance team to ensure posting group assignments are correct before any transactional data loads.

Expand ERP user accounts (name, email, role) map to Dynamics 365 User records. Role-based access structures differ between the platforms; we migrate user identities by email match and flag role mapping as a post-migration configuration step. Any Expand ERP role without a direct Dynamics 365 equivalent is documented in the handoff package for the customer's admin to assign appropriate permission sets.