Migrate from eFacto ERP to Microsoft Dynamics 365 Business Central

eFacto stores account codes and structures in a flat SQL-based chart. We extract the account master (account code, name, type, posting group, and GST/VAT tax code) and map each G/L code to a Dynamics 365 Finance G/L Account with the matching Account Type (Posting, Heading, Total, or Statistics). We flag inactive accounts that must be reactivated at the destination, and we preserve the account structure hierarchy for validation against the Dynamics 365 COA dimensions framework. The migration-as-of date is set to the last closed ledger period so that all balances carry forward correctly into the new system.

eFacto Customer records include billing and shipping addresses, payment terms, GST/VAT registration numbers, credit limits, and price group assignments. We deduplicate by phone and email, preserving the GSTIN/TIN field in a custom Dynamics 365 Customer field, and map the payment terms code to a Dynamics 365 Payment Terms record. Customer hierarchy assignments migrate as parent-customer links if the destination is configured for a hierarchical model.

Vendor records mirror the Customer structure with additional fields for PAN/TIN registration and banking details for electronic payments. We preserve purchase terms, outstanding purchase order references, and PAN/TIN values in vendor-specific custom fields. Vendor hierarchy assignments migrate as parent-vendor links.

Items carry SKU, description, unit of measure, standard cost, and selling price. We map eFacto item types (Stock Item, Service, BOM-based) to Dynamics 365 Product types. BOM structures are split into parent products and BOM lines migrated as bill of materials routes, with the manufacturing warehouse mapping resolved at migration time. Variant data (size, colour, batch, lot) is split into the destination's product variant schema if the destination edition supports variant tracking.

We flag all open invoices, credit notes, and partial payment records and assign them a migration-as-of date consistent with the ledger closing date. Partial payments carry forward as open adjustment lines rather than being reset to zero. Each open transaction preserves the original invoice number, posting date, due date, and outstanding amount so that Dynamics 365 Finance reconciles them correctly against incoming payments post-migration.

Open Sales Orders migrate with full line-item detail, including item number, quantity, unit price, discount, and tax amount. We link each order to the resolved Customer record and flag any orders with a status of Pending, Confirmed, or Partially Shipped. Cancelled or fully fulfilled orders are archived in a separate export file and not imported. Drop-ship and special-order flags map to Microsoft Dynamics 365 Sales Order line configurations.

Open Purchase Orders migrate with full line-item detail, linked to the resolved Vendor record. We preserve receipt status flags so that partially received orders show the correct outstanding quantity at the destination. Completed or cancelled purchase orders are archived and not imported.

eFacto POS receipts are stored in a separate transaction log from the accounting ledger. We aggregate daily POS transactions and map the totals to Microsoft Dynamics 365 Sales Receipts or General Journal lines depending on whether the destination treats POS cash sales as standing invoices or direct cash postings. Each POS receipt number is linked to the corresponding journal entry via a migration mapping table that the customer retains for post-migration reconciliation. Tender type (cash, card, wallet) is preserved in a custom field for bank statement matching.

Current stock quantities are extracted per warehouse and per batch/lot if applicable. We set the stock-as-of date to the migration date and do not migrate historical valuation entries, which are recreated by Dynamics 365 Finance from the COA opening balances. Multi-location assignments migrate by warehouse code, with each warehouse pre-created in Dynamics 365 before inventory import begins to satisfy the InventLocationId lookup.

Employee master records include designation, department, reporting manager, and salary structure details. We map designations to Dynamics 365 HR Job and Position records, and departments to Operating Units. Payroll transaction history is not migrated because it requires re-entry in the destination's payroll module with tax authority recalculation. Active and inactive employee status is preserved.

Custom SSRS reports built with eFacto's Report Builder reference stored procedures that include business logic specific to the eFacto schema. We export the RDL XML and parameter definitions and map the report parameters to the Dynamics 365 reporting schema, but the underlying stored-procedure logic cannot be imported. We deliver the RDL files with a written map of which eFacto tables and fields each report referenced, and the customer's Dynamics 365 partner rebuilds the equivalent reports using Power BI or the Dynamics 365 report designer.

eFacto stores attachments inside its SQL database as BLOBs or file paths. No documented public API exposes these as standalone files. We do not migrate attachments. We deliver a written inventory of all attachment references (document IDs, record associations, and approximate file sizes) so that the customer's eFacto administrator can retrieve them manually from the source system and upload them to the appropriate Dynamics 365 record after migration.