Migrate from Freespace ERP to Microsoft Dynamics 365 Business Central

Freespace ERP organizes accounts around industry-specific modules with cost-center tags. Dynamics 365 Finance and Operations and Business Central use dimensional accounting with financial dimension sets that combine cost center, department, project, and other dimension types. We enumerate every Freespace account code, map its module assignment to the appropriate Dynamics 365 Main Account, and configure financial dimension values that match the source cost-center structure. If Freespace uses custom cost-center naming, we create matching dimension values in Dynamics 365 during the schema phase.

Freespace ERP customer records (name, contact details, billing address, payment terms) map directly to Dynamics 365 Customer. We preserve the payment terms as the Dynamics 365 PaymentTermCode value. Customer addresses map to the LogisticsPostalAddress structure with AddressType = Invoice. Non-alpha ASCII characters in customer names are stripped before import to prevent schema violations in Dynamics 365.

Freespace ERP vendor records map to Dynamics 365 Vendor with the same field-level preservation as customer records. Payment terms migrate as PaymentTermCode, and remittance addresses map to the vendor postal address structure. Non-alpha ASCII characters in vendor names are stripped during the transform phase. Vendor tax information maps to the TaxRegistration entity if present in the source export.

Freespace ERP item masters (SKU, description, unit of measure, standard cost) map to Dynamics 365 Released Product. Unit of measure class maps to the Dynamics 365 UnitOfMeasureClass, and the base unit of measure maps to the item's inventory unit. Site and warehouse assignments from Freespace map to the Dynamics 365 InventorySite and Warehouse entities. For manufactured items with BOM associations, see BOM mapping below.

Multi-level BOM structures in Freespace ERP require an explicit handling decision during scoping: preserve as nested sub-assembly links (BOM lines referencing child BOMs via BOMVersion) or flatten to a single-level BOM explosion. Dynamics 365 supports both models. We present the decision to the customer with a data-driven recommendation based on the number of multi-level structures and the destination's routing model. We compute the BOM explosion cost rollup for validation against the source standard cost.

Open accounts payable documents (invoice number, vendor, document date, due date, amount, payment terms) map to Dynamics 365 VendorInvoiceJournal lines. We chunk export by document date to manage volume and preserve the payment terms as a reference for setting the InvoiceDate and DueDate on the journal. We do not migrate payment history records; these are flagged for reconciliation against the destination's bank reconciliation module post-migration.

Open accounts receivable documents map to Dynamics 365 FreeTextInvoice or SalesInvoiceHeader depending on whether the source invoice has been posted. Document date, due date, amount, and customer reference map to the equivalent Dynamics 365 fields. Credit memos map to FreeTextInvoice with negative amounts or to CreditNote depending on the destination's invoice model configuration.

Freespace ERP production orders with multi-stage workflow names, quantities, and material consumption links map to Dynamics 365 ProductionOrder. User-defined stage names in Freespace become custom production order status values or ProdRouteJob status entries in Dynamics 365. We resolve the BOM reference and route reference at migration time and validate that the production order quantities align with the bill of materials and routing in the destination.

Freespace ERP work orders for maintenance or job-costing map to Dynamics 365 AssetManagementWorkOrder or the Project module's WorkBreakdownStructure depending on the source work order type. We extract the cost center, work type, priority, and estimated hours from Freespace and map them to the corresponding Dynamics 365 work order dimensions. If Freespace uses job-costing hierarchies, these map to the ProjectContract and Project entities with CostCategory assignments. This object mapping covers the full work order lifecycle including labor assignments and material consumption links.

Freespace ERP transaction history (production orders, material issues, inventory movements) maps to Dynamics 365 InventTrans with posting date preserved. We chunk by date range (quarterly or annual windows) to manage volume and use batch inserts with inventory posting profiles mapped from the source cost-center to the destination dimension set. Journal entry line sequences and dimension tags are preserved in the inventTransDimension field.

Freespace ERP journal entries (header with posting date, account code, debit/credit amounts, and dimensions) map to Dynamics 365 GeneralJournalAccountEntry or LedgerEntryDetail depending on whether the destination uses the financial dimension model or the legacy dimension model. Line item sequence and dimension tags from Freespace are mapped to the corresponding dimension set in Dynamics 365. We validate that debit and credit totals balance after the transform.

Freespace ERP employee profiles (name, department, job title, hire date, employment status) map to Dynamics 365 Human Resources Worker. Department maps to the Legal Entity and HR Department; job title maps to Position. Employment status (active, inactive, terminated) sets the WorkerStatus or ValidFrom/ValidTo temporal fields. Custom employee properties added via Freespace's field management UI are mapped to Worker custom fields or the HcmWorkerExtensionEntity.

Freespace ERP effective-dated compensation rows (salary or wage rates, pay frequency, deduction codes) map to Dynamics 365 HcmCompensationFixedPlan with effective date sequencing preserved. Retroactive adjustments that create rows with effective dates earlier than the record creation date are flagged and sorted by effective date before import, ensuring a chronologically consistent compensation timeline. Pay frequency maps to the CompensationFrequency entity. We do not migrate payroll tax calculations; those are reconfigured in Dynamics 365 Payroll based on the legal entity tax setup.