Migrate from Finesse ERP to Microsoft Dynamics 365 Business Central

Finesse Customer records map directly to the Dynamics 365 customer entity. The customer ID, name, address, contact information, payment terms, credit limit, and tax ID migrate as typed fields. Multi-address customer records in Finesse (ship-to and bill-to) split into separate Customer Addresses in Dynamics 365. In Finance and Operations, the Customer account number must satisfy the number sequence configured in the destination Legal Entity before import. We extract Finesse customer records first in the migration sequence so that AccountID references are available for all downstream transactional imports.

Finesse Vendor master data, including bank details, W-9 information, payment terms, and multi-address records, migrates to the Dynamics 365 vendor entity. Ship-from locations in Finesse become separate Vendor Addresses. Vendor account numbers in Finance and Operations must match the destination number sequence, and any vendor records with incomplete W-9 data are flagged for pre-migration reconciliation to prevent 1099 filing errors post-go-live.

The Finesse GL account structure migrates with full segment support. We preserve account types (Asset, Liability, Equity, Revenue, Expense), account descriptions, and intercompany account flags. Active versus inactive status carries over explicitly to prevent post-migration posting errors. Finesse segment values (cost centers, departments, locations) map to Dynamics 365 financial dimensions configured as dimension sets in the destination, and the dimension combination is validated against the destination's account structure before import.

Finesse Items map to the Dynamics 365 product master. The item number, description, item category, unit of measure, cost method (standard, average, FIFO), and default warehouse migrate as standard fields. Manufacturing-specific attributes from Finesse (planning method, scrap percentage, Phantom BOM flag) map to the corresponding Dynamics 365 production and costing configuration fields. Stock and non-stock item distinctions carry over as the product type in Business Central or the Product type in Finance and Operations.

Finesse BOMs embedded within item records must split into separate BOM entity records in Dynamics 365. Each Finesse BOM line (component item, quantity per, bom position, operation number, scrap percentage) maps to a BOMLine or Production BOMLine entity with the appropriate header reference. We extract BOM header and line data separately from Finesse, generate BOM numbers from the parent item number plus a sequence suffix, and validate that component items exist in the destination before BOM lines are inserted. Multi-level BOMs (parent with sub-assemblies) are resolved in bottom-up order to ensure sub-assembly BOMs are available before parent BOM insert.

Finesse routing data embedded within items must split into separate Route and Work Center entities. Work Center capacity data (efficiency factor, queue time, setup time, run time) from Finesse maps to the Dynamics 365 Work Center Capacity schema. Route Operations sequence numbers and the routing-to-operation linkage in Finesse map to Route Operations with the appropriate Work Center reference and operation number ordering. In Finance and Operations, the route must be attached to a specific BOM version on the Released Product before production order generation.

Finesse Projects aggregate jobs, cost variance, and milestones under a single project header. We extract project headers with status, cost budget, cost-to-complete, and milestone dates, then map them to Dynamics 365 Project entities with the appropriate project type (Time and Material, Fixed Price, or Internal). Finesse's cost variance fields become Project Forecast lines or Project Budget lines depending on the destination project type. For companies using Finesse's ETO mode, the Project type in Dynamics 365 is set to Time and Material with billing rules configured per project contract.

Finesse Jobs represent the manufacturing execution unit and carry start dates, quantity, priority, cost tracking, and job cost lines. For Finance and Operations destinations, Finesse Jobs map to Production Orders with estimated route and BOM consumption. For Business Central destinations, Jobs map to Manufacturing Work Orders with linked production BOM and routing references. Labor and material postings from Finesse job cost lines map to Production Journal lines or Project Journal lines depending on whether the destination uses production costing or project costing. Open jobs (status not Closed) are prioritized for migration; closed jobs may be migrated as historical records or retained as summary data at the customer's discretion.

Open Finesse AP invoices migrate as unpaid vendor invoice records with full line-item detail to preserve aging accuracy. Vendor references are resolved to destination Vendor accounts via the vendor mapping. Invoice numbers, invoice dates, due dates, and payment terms carry over. Credit memos migrate as negative invoice lines or credit note records. We flag any Finesse AP records with nested approval holds or exceptions for manual review before destination activation to prevent payment processing errors on migrated open items.

Open Finesse AR invoices and unapplied payments migrate with full aging detail. Customer references are resolved to destination Customer accounts. We preserve invoice numbers, invoice dates, due dates, and payment terms. Unapplied customer payments migrate as open journal lines that the AR team reconciles post-migration. Any AR records with nested dispute flags, credit holds, or collection status are flagged for manual review before destination activation. The AR aging report in Dynamics 365 is validated against the Finesse aging report as a reconciliation checkpoint.

On-hand quantities by location and lot number migrate to the destination inventory module with transaction date set to the migration snapshot date. We flag any Finesse negative quantities or quantities below safety stock for pre-migration reconciliation because Dynamics 365 enforces posting inventory on-hand restrictions that Finesse may not have enforced. Lot and serial number information from Finesse maps to the corresponding lot tracking schema in Dynamics 365. Inventory valuation (standard cost, average cost) carries over from Finesse's cost layer to prevent valuation discrepancies in the first post-migration financial close.

Active Finesse Users migrate to Dynamics 365 User records, with roles and security permissions mapped to the destination's permission sets or security roles. We extract user email addresses as the dedupe key for matching. Department assignments and team memberships from Finesse map to Dynamics 365 Teams and Workplace structures. Inactive Finesse users are exported with their status for the customer's admin to deactivate or archive post-migration. In Finance and Operations, HcmWorker records (HR-linked workers) require an HR worker record as a prerequisite before the User record can be activated, adding a dependency that we sequence before user import.

Finesse user-defined fields on master and transaction records are exported with their definitions and values. We map each custom field to the destination's equivalent custom field mechanism: in Business Central, custom fields are added via AL extensions; in Finance and Operations, they are added via the extension framework or by extending the EDT. The customer chooses whether to replicate all custom fields or a prioritized subset during scoping. Custom field values are held in a staging table and inserted after the base record is committed in the destination.

Documents stored in Finesse (drawings, specs, photos, PDF attachments) are exported via file reference extraction or direct file copy depending on the Finesse storage backend. We map documents to the corresponding Dynamics 365 Document Handling or SharePoint integration depending on the destination configuration. Documents older than the customer's retention policy threshold are flagged for review before migration to reduce blob storage costs in Dynamics 365. Engineering drawings linked to BOM components in Finesse are mapped to the corresponding product or BOM document attachment in Dynamics 365.

Historical Finesse job cost records (labor postings, material consumption, overhead allocations) migrate as journal lines for audit and historical reporting purposes. These records are not re-posted as live transactions but are stored as reference records attached to the migrated Production Order or Project. The job cost category (labor, material, overhead) from Finesse maps to the appropriate posting profile in Dynamics 365 so that historical totals align with the destination's cost category structure. Cost amounts are preserved in the original currency for companies with multi-currency records.