Migrate from De Facto ERP to Microsoft Dynamics 365 Business Central

De Facto customer master records map to Microsoft Dynamics 365 F&O CustTable or Business Central Customer records. We preserve customer name, primary contact details, addresses (resolving the De Facto multi-address-per-purpose model into D365's one-primary-address constraint), payment terms, and currency assignments. Account balance at migration date migrates as an opening transaction in D365's fiscal journal rather than as a live balance field, since D365 does not carry forward aged balances in the same way as De Facto.

De Facto vendor master records including addresses, payment terms, bank details, and multi-country tax codes map to D365 VendTable or Business Central Vendor. We preserve currency assignment, tax registration numbers, and WHS (Warehouse Management System) vendor lead times as part of the supplier record. The vendor's payment terms and charges agreement migrate to D365's vendor payment terms and charges setup tables.

De Facto stock items map to D365 F&O EcoResProduct (released product) and InventTable (inventory dimension tracking), or Business Central Item records. Item number, description, unit of measure, product type (stockkeeping, service, non-stock), and storage dimensions (site, warehouse, location) migrate directly. Item costing model (standard, moving average, FIFO) from De Facto maps to the D365 costing version and cost group configuration.

De Facto BOM structures migrate to D365 F&O BomTable and BomLine, or Business Central production BOM. Multi-level BOMs (BOMs containing sub-assemblies that are themselves BOMs) require recursive resolution during scoping because De Facto's BOM export may flatten or nest structures differently than D365's indented BOM model. We validate the bill of materials path and production route before migration to avoid phantom BOM errors in D365.

De Facto's landed-cost tracking stores freight, insurance, duty, and tax as item-level or shipment-level cost components that must split into D365 F&O's landed cost model (LandedCost table with LandedCostLine for each charge type) or Business Central's additional cost posting. We extract the cost component breakdown from De Facto's TSQL output, then create D365 LandedCost vendors (freight forwarder, customs broker) and assign cost groups to each charge type so that inventory valuation reflects the full landed cost per item.

Open invoices, credit notes, and outstanding balances from De Facto migrate to D365 F&O open invoice tables (CustInvoiceJour for AR, VendInvoiceInfoTable for AP) with payment status preserved. We set the invoice status in D365 to Open or Pending rather than Paid, and we flag any overdue items with the original due date and days outstanding. Reconciliation against the De Facto trial balance happens before and after migration to confirm no amounts are double-posted or dropped.

De Facto's chart of accounts exports cleanly via TSQL as a structured CSV or XML output. We map De Facto account numbers and descriptions to D365 F&O MainAccount or Business Central G/L Account. Account type (Revenue, Expense, Asset, Liability, Equity) maps to D365's account type and posting definition. If De Facto uses a multi-segment account structure (e.g., 4-2-2-2), we configure D365's financial dimension framework or account structure to match so that posting profiles resolve correctly.

De Facto fixed asset registers including acquisition cost, depreciation schedules (straight-line, reducing balance, units of production), and asset locations migrate to D365 F&O AssetTable and AssetBook, or Business Central Fixed Asset records. We extract the current net book value and remaining depreciation from De Facto, then create D365 asset records with the acquisition date, cost, and a depreciation proposal set to the next depreciation run date to preserve the asset's accounting state.

De Facto user records and role assignments migrate to D365 UserInfo or Business Central User records. Role definitions are often highly custom in De Facto and do not map 1:1 to D365's security role model. We extract all users with their role memberships and a list of companies or data partitions they can access, then map the most common roles (AP clerk, inventory manager, accountant, sales rep) to the nearest D365 security role. Any De Facto role without a D365 equivalent goes to a written security mapping table for the customer's admin to assign manually.

De Facto CRM opportunities with name, estimated value, stage, expected close date, and associated contacts migrate to D365 F&O CustSalesOpportunity or Business Central Sales Opportunity. Stage values map to D365's sales pipeline stage names, and probability percentages map to stage weights. Any custom CRM fields in De Facto (for example, solution type, competitor flags, or renewal probability) become D365 custom fields on the opportunity entity.

De Facto stores documents linked to data records and supports inbound OCR auto-storage with barcode/QR reading. We extract document files (PDFs, images, Office documents) and the document-to-record linkage table from De Facto's database. Each document migrates as a DocuRef record in D365 F&O or a Document record in Business Central, linked to the corresponding Customer, Vendor, Item, or Transaction record by primary key. OCR metadata and barcode data do not migrate to D365 equivalents; we deliver a separate document inventory listing what was linked and to which record.

De Facto's full transaction history including purchase orders, sales orders, warehouse movements, and general ledger postings can be exported via TSQL script output. Large transaction volumes require chunked extraction by fiscal period (typically quarterly or annually). We migrate open and recently closed periods fully and archive historical periods older than three to five years (the scope is agreed during discovery). Each transaction type maps to its corresponding D365 table: inventory movements to InventTrans, GL postings to FiscalJournalTrans, purchase orders to PurchTable and PurchLine, and sales orders to SalesTable and SalesLine.

De Facto's warranty stock management for importers tracks replacement inventory held separately from normal stock. We map warranty stock locations to D365 F&O quarantine orders (QuarantineOrder table) or Business Central stockkeeping units with a specific warehouse location flagged as warranty. The warranty item's costing method and tracking requirements migrate to D365 inventory model settings, and any open warranty claims in De Facto become D365 quality orders or service orders.

De Facto's Reporting & Analysis module uses Microsoft SSRS-based report definitions that are not portable across platforms. We do not migrate SSRS reports. Instead, we extract the report metadata (report name, parameters, data sources, filters, and the TSQL queries or stored procedures that feed each report) and deliver it as a written report inventory. The customer's D365 admin or reporting partner uses this inventory to rebuild equivalent reports in D365 using SSRS (on-premises F&O), Power BI, or D365's built-in financial reporting.