Migrate from Freedom ERP to Microsoft Dynamics 365 Business Central

Freedom ERP Customer records map to Microsoft Dynamics 365 Customer entities. In Finance & Supply Chain Management, this is the CustTable data entity; in Business Central, it is the Customer table. We preserve Customer name, GST registration number (for India compliance), billing and shipping addresses, payment terms, credit limit, and contact details. GSTIN maps to the Tax Identification Number field. The primary address becomes the Invoice address; if a separate delivery address exists in Freedom ERP, we map it as a secondary address in D365. Customer-specific pricing or discount groups migrate as Customer Price Groups.

Freedom ERP Vendor master records map to D365 Vendor entities (VendTable in Finance & Operations; Vendor in Business Central). We preserve vendor name, PAN and GST registration, payment terms, bank details, and any linked PO or GRN history that the customer elects to include in migration scope. Vendor-specific GST TDS rates migrate as withholding tax groups configured in D365 Finance. If the vendor is also a customer (common in job-work scenarios), we create both a Vendor and a Customer record with the same party.

Freedom ERP Items—raw materials, intermediates, and finished goods—map to D365 Released Products. We preserve item number, description, item type (Stockkeeping, Service, BOM), unit of measure, cost price, standard cost, and warehouse assignment. Item type distinguishes whether the item is stocked, a service, or a BOM component. Multiple unit-of-measure conversions defined in Freedom ERP (e.g., piece-to-kg, dozen-to-piece) migrate as Unit of Measure Groups in D365. The primary warehouse and location assignment from Freedom ERP maps to the default warehouse on the released product.

Multi-level BOMs in Freedom ERP require explicit tree reconstruction before migration. We extract the full BOM hierarchy—parent items, component items, quantities per assembly, phantom BOM flags, scrap percentages, and routing operations—from the database and build a BOM version in D365 Finance and Supply Chain Management or Business Central Manufacturing. Phantom assemblies in Freedom ERP (components that exist only within the parent BOM) become phantom BOM lines in D365. Co-products and by-products defined in Freedom ERP manufacturing orders migrate as BOM line types configured per the customer's costing method. This step adds a planning day to the migration schedule but is required because BOM copy-paste between platforms does not preserve the parent-child lineage.

Freedom ERP COA records map to D365 Main Accounts. We preserve account number, account name, account type (Asset, Liability, Income, Expense, Equity), account group, and GST/S-tax mapping. Cost center assignments stored in Freedom ERP as sub-account dimensions migrate to D365 Financial Dimensions configured during the destination setup phase. Indian-specific account structures (such as TDS Payable, CST Receivable) map to the equivalent ledger accounts in D365 Finance. The customer chooses whether to use the standard D365 COA layout or map Freedom ERP's account numbering scheme directly.

Outstanding receivables and payables migrate as open invoices in D365. Freedom ERP AR records (customer invoices, credit notes, receipts) map to Customer Invoice or Free Text Invoice lines with invoice number, customer account, invoice date, due date, amount, and GST amount. Vendor AP records (vendor bills, debit notes, payments) map to Vendor Invoice lines. We preserve the payment status (open, partial, closed) and link each invoice to the corresponding customer or vendor record. Locked or disputed invoices are flagged in a migration status field for the customer's finance team to review before closing in the destination.

Freedom ERP Production Orders—work orders linked to BOMs, work centers, and scheduling dates—map to D365 Production Orders. The mapping is contingent on the customer's manufacturing mode (discrete manufacturing, process, or job work) as defined during discovery. We extract production order number, item to be manufactured, quantity, scheduled start and end dates, status, and routing operations. If the production order references a specific BOM version in Freedom ERP, we link it to the migrated BOM version in D365. Closed and completed production orders migrate as historical records; open orders migrate as active Production Orders requiring production scheduling in D365.

Freedom ERP Employee records map to D365 Human Resources Workers. We preserve employee number, name, date of birth, date of joining, department, designation, reporting manager, employment type (full-time, contract), and company assignment. Active and inactive employees both migrate; inactive status is preserved as a Worker status value. Org hierarchy from Freedom ERP (reporting chains, departmental structure) maps to D365 HR position hierarchies. If Freedom ERP stores bank account details for payroll, we migrate those as separate payment information records in D365 HR.

Payroll data including salary components, deductions, and payrun history migrates as summary pay statement records in D365 Human Resources or via a certified India payroll ISV (since D365 HR does not include a native India payroll engine). We export payrun summaries—employee, pay period, earnings breakdown (basic, HRA, allowances), deductions (PF, ESI, TDS), and net pay—preserve the most recent two fiscal years for audit purposes, and load them as historical pay statements. Detailed earning line history (per-pay-component records) is mapped if the source schema supports it. Active salary configuration (pay grades, structures) is delivered as a written configuration guide for the customer's HR admin or payroll ISV partner to set up in D365.

QC inspection records linked to production lots and item batches in Freedom ERP map to D365 Quality Orders (Finance & Supply Chain Management) or Quality Management extension (Business Central). We extract inspection lot number, item, quantity inspected, inspection result (Pass/Fail), defect codes, and inspector assignment. Custom inspection criteria fields defined in Freedom ERP (often stored in non-standard tables) are audited during schema discovery and remapped to D365 Quality Association template fields. QC results linked to specific production orders are associated via the production order reference.

Equipment and machine maintenance logs from Freedom ERP—work orders, spare parts consumed, technician assignments, and maintenance type—map to D365 Asset Management work orders (Finance & Supply Chain Management) or the Maintenance module in Business Central. We preserve the asset linked to the work order, failure reason, maintenance type (preventive, corrective), and cost. Spare parts consumed migrate as product lines on the work order. Work order status (open, in progress, completed) maps directly to D365 work order lifecycle stages.

Gate entry records tracking inward and outward material movement—vehicle number, challan reference, material description, quantity received or dispatched, and timestamp—migrate as warehouse receipt lines or inventory transfer records in D365. We extract the structured gate entry data from Freedom ERP as a structured export and load it into D365 Inventory Management as inbound shipment or transfer order lines. Gate entry document references are preserved in the D365 document handling or notes field for traceability.

Freedom ERP project definitions, milestones, tasks, and resource assignments map to D365 Projects (Project Management module in Business Central or Project Operations for professional services scenarios). We preserve project name, project number, start and end dates, project status, WBS hierarchy, task list, and resource assignments. If Freedom ERP tracks project-specific billing or cost accruals, those migrate as project transactions in D365. Project costing methods (time and material vs fixed price) map to the D365 project type.