Migrate from Standard ERP to Microsoft Dynamics 365 Business Central

Standard ERP's structured GL chart with parent-child hierarchy, account type, currency code, and cost-center assignments maps to Dynamics 365 MainAccount or G/L Account with the account number as the primary key. We extract the full account hierarchy including account type, currency, and cost-center assignments and replicate it in the target with proper parent-child relationships. Standard ERP cost-center assignments map to Financial Dimensions in Finance and Operations or as a separate Dimension Code in Business Central. We flag any Standard ERP accounts with currency codes not present in the Dynamics 365 exchange rate table for admin setup before the GL migration phase.

Standard ERP Customer records including billing and shipping addresses, payment terms, and contact associations migrate to Dynamics 365 CustCustomerV3Entity or Business Central Customer. We preserve customer-specific pricing tiers as custom fields in the destination. Address records in Standard ERP with multiple addresses (billing, shipping, plant) map to LogisticsPostalAddress with the AddressType field set; Finance and Operations allows multiple addresses but only one marked as Primary, so we designate the billing address as Primary and hold the others for admin assignment post-migration.

Standard ERP Vendor master records including bank details, 1099 flags, and purchase terms migrate to Dynamics 365 VendVendorV2Entity or Business Central Vendor. We validate vendor address formats against the destination's country-specific requirements and map 1099 reporting flags to the corresponding tax registration fields in Dynamics 365. Payment terms from Standard ERP map to the PaymentTerms lookup table in the destination.

Standard ERP Item records include inventory, non-inventory, and service variants with BOM linkages. We map BOM structures and variant definitions to the destination's item schema. Inventory items migrate to EcoResProductV2Entity (product master) with InventItemEntity (item-specific inventory and costing settings) in Finance and Operations, or to Item with Item Tracking and Unit of Measure in Business Central. BOM lines migrate as production Bill of Materials records. We flag any Standard ERP items with costing methods (Standard, Average, FIFO) that require corresponding costing version setup in Dynamics 365.

Outstanding vendor invoices, credit memos, and payments are extracted from Standard ERP with full aging detail and mapped to VendInvoiceJournalLine (Finance and Operations) or Vendor Ledger Entries (Business Central). We match open documents to their corresponding GL entries to ensure balances reconcile post-migration. Standard ERP's open AP aging buckets map to Dynamics 365's Due Date aging structure. Prepayments and partially paid invoices are flagged as partial-payment records requiring settlement mapping after migration.

Outstanding customer invoices, credit memos, and payments migrate to CustInvoiceJournalLine (Finance and Operations) or Customer Ledger Entries (Business Central). We extract the full aging detail including invoice date, due date, discount terms, and payment status, then map to the corresponding Dynamics 365 invoice and payment records. Customer payment terms and cash discounts are preserved as PaymentTerms and CashDiscountCode on each invoice record.

Standard ERP stores closed periods separately from open ones. We extract the full transaction register including journal entries and map them to the destination's fiscal periods. Closed period migration requires either temporary period reactivation on the source system or reconstruction of journal entries as current-period adjustments in the destination. We preserve the original posting date, voucher number, and source ledger on each GeneralJournalAccountEntry for audit trail purposes. Multi-currency transactions carry the effective-date exchange rate from Standard ERP and are re-evaluated against the Dynamics 365 exchange rate table at go-live.

Standard ERP job costing links labor, materials, and overhead to specific projects with phase-level breakdowns. We map these to Dynamics 365 Project management (ProjProjectEntity) with project phases as WBS nodes, or to Business Central Jobs with Tasks and Deliverables. Hour categories, billing types, and cost price models migrate as project pricing structures. We flag any Standard ERP job cost categories that lack a corresponding category group in the destination for admin configuration before the project migration phase.

BOM-linked production orders include routing, work-center assignments, and actual versus estimated cost data. We transfer the production order header and line structure to ProdProductionOrderEntity or Business Central Production Order. Routing detail with work-center sequences may require post-migration configuration in the destination's route and work-centers setup. Estimated costs migrate as cost estimates; actual costs migrate as production posting journals. We flag any production orders in Released or In-Process status that require exception handling during cutover.

Standard ERP stores document attachments in a proprietary internal vault. We extract vault packages via HAL script or direct database query, then associate them with migrated records using a filename-to-record-ID mapping table built during discovery. Large attachment volumes may require staged transfer. In Dynamics 365 Finance and Operations, we upload files to SharePoint Online or Azure Blob Storage and create Document Handling references linked to the parent entity. In Business Central, attachments migrate to the Document Attachment functionality with a cross-reference table. File type conversion (proprietary format to standard PDF or Office) is handled per file during extraction.

Standard ERP User accounts, roles, and permission sets migrate as a role-mapping exercise. We map Standard ERP user IDs to Dynamics 365 Employee records (Finance and Operations) or User contact persons (Business Central), then coordinate with the customer to map roles to the destination security roles. Any permissions that lack a direct equivalent are flagged in the security role mapping document delivered at the end of migration. We do not configure Azure Active Directory synchronization or Teams integration as part of the data migration scope.

HAL-scripted custom fields, workflows, and integrations have no direct equivalent in Dynamics 365's standard data model. We catalog every HAL customization during discovery, map each to a destination custom field (AL extension in Business Central, custom field on the entity in Finance and Operations), or document it as a manual procedure. HAL custom integration endpoints (warehouse management, third-party APIs) are documented with their data source and destination for the customer's IT team to reimplement using Power Automate or the Dynamics 365 OData API. HAL customization mapping is scoped and quoted separately from the base migration.