Migrate from etEngine to Microsoft Dynamics 365 Business Central

etEngine account codes, names, and types map to Dynamics 365 General Ledger MainAccount records. Currency assignments and department codes migrate as financial dimensions or posting groups depending on the destination edition (Business Central vs Finance). We preserve the original account structure in a custom field src_account_code__c for reconciliation. Multi-segment account codes (e.g., 1000-010-CASH) split into the MainAccount number and financial dimension values per the Dynamics 365 account structure definition.

etEngine Customer records map to Dynamics 365 Customer with contact details, billing addresses, and payment terms preserved. The customer number from etEngine becomes the Customer Number in Dynamics 365; if etEngine uses an auto-increment integer, we recommend setting a number series prefix during configuration to avoid conflicts. Address books with multiple locations map to the Dynamics 365 address book structure with one address designated as the primary invoice address.

etEngine Vendor master records map to Dynamics 365 Vendor with contact information, payment terms, and bank account details preserved. Vendor-specific dimensions (cost center, purchasing organization) from etEngine custom fields map to Dynamics 365 financial dimensions or extended text fields depending on the destination schema. We flag any vendor records with incomplete W-9 or tax registration data for remediation before migration.

etEngine Item masters including SKUs, descriptions, unit of measure, cost, and pricing map to Dynamics 365 Item cards. Product type (Inventory, Service, Non-Inventory) is determined during scoping based on etEngine item classification. Variants and custom attributes on items migrate as item cross-references or custom fields. Pricing structures (list price, discount agreements) map to Microsoft Dynamics 365 Sales Prices and Purchase Prices with the same currency and customer or vendor assignment.

Outstanding customer invoices from etEngine map to Dynamics 365 CustInvoiceJour and CustLedgerEntry with original invoice dates, amounts, and due dates preserved. Vendor invoices map to VendInvoiceJour and VendLedgerEntry. We flag any invoices marked as reconciled in etEngine that should not be carried forward to avoid duplicate posting. Open vs closed status determines whether records land in the transaction journal or ledger entry tables. Remittance advice lines and payment terms are preserved to support partial payment tracking in Dynamics 365.

Past journal entries from etEngine are chunked by fiscal period and loaded into Dynamics 365 in chronological order to maintain audit trail integrity. Customer and vendor transaction histories migrate to CustTrans and VendTrans respectively with posting dates, document numbers, and amounts. Inventory transactions migrate to ItemLedgerEntry with location and variant assignments. We coordinate with your Dynamics 365 admin to ensure the fiscal year setup in the destination allows posting to historical periods, or we configure a closed-period workaround with appropriate security roles.

etEngine User accounts map to Dynamics 365 User records with active or inactive status preserved. Role and permission assignments from etEngine map to Dynamics 365 permission sets or security groups. We create a role mapping matrix during scoping that assigns each etEngine role to an equivalent Dynamics 365 role (e.g., etEngine Accountant to Dynamics 365 BASIC user with Finance permissions). Users without a matching email in the destination tenant go to a reconciliation queue for the admin to provision before production migration.

etEngine-attached files and linked documents are exported to a file store (Azure Blob Storage or SharePoint Online) and re-linked to their corresponding records in Dynamics 365 via document handling or the SharePoint integration. File naming conventions preserve the original document context (e.g., INV-2024-0042.pdf). We document the SharePoint library structure and attach each file to the related Customer, Vendor, or Item record using Dynamics 365 document attachment capabilities.

etEngine payment term definitions (Net 30, Net 60, 2/10 Net 30) map to Dynamics 365 Payment Terms with the same due date calculation logic preserved. Discount percentages and discount period windows transfer as-is to ensure early payment discount calculations work correctly in the destination. Custom payment terms are flagged for manual configuration in Dynamics 365 if they use non-standard day counts.

etEngine shipping method codes map to Dynamics 365 Shipment Method records. The shipping account numbers and carrier-specific settings are preserved as extended text fields. Integration points with carrier systems (e.g., FedEx, UPS) are documented for reconfiguration post-migration if the destination includes the Transportation Management module.

etEngine tax codes and rates map to Dynamics 365 Tax Group and VAT Business Posting Group combinations. We extract the tax configuration from etEngine during scoping and design the equivalent Dynamics 365 tax posting setup. Sales tax vs VAT jurisdictions require separate configuration branches. Tax-exempt customers and vendors receive Tax Exempt Number assignments in Dynamics 365. This is a configuration step the customer performs with their tax advisor rather than a data migration step.

etEngine custom fields on Customers, Vendors, and Items map to custom fields on the corresponding Dynamics 365 tables. We use table extensions in Dynamics 365 Finance and Business Central to add these fields without modifying the base schema. Field data types are mapped: text fields to Text or Option for enums, numeric fields to Decimal or Integer, date fields to Date. Lookup fields to other custom entities require the target custom field to exist first, so we sequence custom field creation before data migration.