Migrate from Focus ERP to Microsoft Dynamics 365 Business Central

Focus ERP's Chart of Accounts with parent-child hierarchies and account types maps directly to Dynamics 365 main accounts. We preserve account codes, descriptions, and account type assignments exactly. Focus ERP segment columns used for cost-center tracking map to Dynamics 365 financial dimension sets, which are configured in the destination before import. Any inactive accounts in Focus ERP are imported as inactive in Dynamics 365 using the same activation-date logic.

Focus ERP customer records with billing addresses, payment terms, and tax registration numbers migrate 1:1 to Dynamics 365 Customer. We deduplicate on customer name and address combination where multi-company Focus ERP instances created duplicate customer records across entities. Customer price groups and payment schedules map to Dynamics 365 CustGroup and PaymTermId. Tax registration numbers migrate to the TaxInformation table on the CustomerV3Entity.

Focus ERP vendor master records migrate to Dynamics 365 Vendor using the same 1:1 mapping pattern as Customer. Payment terms, W-9 and tax ID fields, and vendor groups map to VendGroup and PaymTermId. Multi-company vendors present in multiple Focus ERP cost centers are consolidated into a single vendor record in Dynamics 365 with separate vendor addresses per legal entity.

Outstanding receivables in Focus ERP carry invoice numbers, due dates, outstanding amounts, and partial payment history. We map these to Dynamics 365 CustTrans (customer transactions) and CustInvoiceJour (invoice journals). Records with partial payments or credit memos require split-line treatment: we extract each partial payment as a separate CustTrans line and flag records where the total paid does not equal the original invoice amount, asking the customer to confirm resolution before committing the load.

Outstanding payables migrate to Dynamics 365 VendTrans and VendInvoiceJour using the same split-line approach as Open AR. Focus ERP vendor invoices with partial payments and debit memos are decomposed into individual VendTrans lines with matching InvoiceId and PaymentId references. We flag any AP record where the payment status is ambiguous due to misaligned invoice dates in the source system.

Focus ERP item masters with SKUs, descriptions, cost prices, selling prices, and stock levels export directly to Dynamics 365 EcoResProduct (released products) and InventItem table. Min/max replenishment rules and reorder-point configurations migrate as InventItemOrderSettings custom fields. Stock levels export to InventDim and InventSum. Item storage dimensions (site, warehouse, location, color, size) map to the relevant InventDim combinations in the destination.

Open and historical purchase orders map to Dynamics 365 PurchTable and PurchLine. Focus ERP line-item tax codes and discount percentages require explicit value-mapping against Dynamics 365 tax code configuration (TaxGroup and TaxItemGroup) before load, as country-specific tax structures do not align automatically. Closed purchase orders migrate as historical records; open purchase orders retain their approval status and can be processed further in Dynamics 365.

Sales orders migrate to Microsoft Dynamics 365 Sales Table and SalesLine with order status, pricing, and line-item data preserved. Discount percentage and tax code mapping apply the same explicit value-mapping process used for purchase orders. Dynamics 365's dimensional inventory model requires that all line items reference a released product; any Focus ERP item not yet released in the destination must be provisioned before the sales order import phase.

Focus ERP field-service and job-tracking records carry custom status workflows, technician assignments, and job-percentage progress fields. We map status values to Dynamics 365 Project status equivalents and preserve technician assignments as Resource and Worker records. If the destination includes Dynamics 365 Field Service, work orders map to the BookableResourceBooking entity; otherwise, they map to Project journal entries. Job-percentage progress migrates as a custom field on the project.

Asset registers include acquisition dates, depreciation methods, and book values. Depreciation schedules require recalculation in Dynamics 365 based on the destination's fiscal year and depreciation profile configuration, so we extract the full asset register including the accumulated depreciation balance from Focus ERP and set the asset to a 'migrated' status in Dynamics 365 with a one-time catch-up depreciation event post-import. The customer's accountant validates the acquired value and remaining book value before the first depreciation run.

Focus ERP user accounts and role permissions export from the user table. Role naming conventions differ between Focus ERP and Dynamics 365, so we extract user-level permission assignments and map them to equivalent Dynamics 365 Security Roles. The customer's admin validates the mapping during sandbox validation and assigns any roles that require manual provisioning. Inactive users in Focus ERP are imported as inactive in Dynamics 365.

Custom fields added via Focus ERP's form builder are stored in extended tables. We extract these as key-value pairs and attach them as extension fields on the corresponding Dynamics 365 entity. Complex custom objects or cross-entity lookup relationships may require schema adjustments in Dynamics 365, which we document and validate during sandbox testing. Any custom field that cannot map directly to a typed Dynamics 365 field is preserved as a text field with a documented original format for post-migration cleanup.