Migrate from Reflex ERP to Microsoft Dynamics 365 Business Central

Reflex stores account codes, descriptions, account types, and inactive flags in its GL table. Dynamics 365 uses a G/L Account table with Account Category (mapping from Reflex account type), posting definitions, and dimension defaults. We extract all account records preserving account code, description, account type, and inactive status. In D365 BC we create G/L Accounts with the matching account number and set the Account Category from Reflex account type; in D365 F&O we map to the LedgerChartOfAccounts structure. Inactive accounts are migrated as inactive and reactivated post-migration at admin discretion. Multi-segment account codes (e.g., 4-2-1000) are preserved as-is or split into separate Main Account and sub-account dimensions depending on the D365 chart of accounts design agreed during scoping.

Reflex Customer master records include billing address, shipping address, payment terms, credit limits, currency, and contact details. We extract all fields including any custom fields attached to the customer record. In D365 BC customers map to the Customer table with payment terms code, credit limit (converted to local currency), and address records. In D365 F&O we write to CustTable with DirParty for name and address structures. Open AR invoices are linked by customer number post-migration using the resolved Customer number as the parent reference. Credit memos and prepayments are flagged separately because they map to different posting profiles in D365.

Reflex Vendor master records mirror the Customer structure with address, payment terms, 1099 settings, and credit limits. We extract all vendor fields and map to D365 BC Vendor or F&O VendTable. The 1099 settings from Reflex (1099 type, box values) map to the US Tax 1099 reporting section in D365. Canadian vendors without 1099 requirements get a Tax 1099 flag set to No. Vendor IDs are preserved as vendor numbers in D365 for AP aging and PO history continuity. Open AP invoices are linked by vendor number post-migration.

Reflex Items carry part numbers, descriptions, costing methods (FIFO, average, standard), pricing tiers, and unit of measure. We extract all item records and map costing method to D365 inventory posting setup: Reflex FIFO maps to FIFO, Reflex average maps to Average, Reflex standard maps to Standard. In D365 BC we create Items with the costing method set; in F&O we use EcoResProduct with costing versions and cost groups. Unit of measure conversions from Reflex's UOM table map to D365's unit of measure setup. Item pricing tiers migrate as sales prices or purchase prices attached to the item.

Reflex BOM structures define component items, quantities, bill of material steps, and routing for manufactured items. We extract BOM headers and all BOM lines with component item references and quantities. In D365 BC we create Manufacturing BOMs with the same structure and attach routing versions if Reflex work orders include labor routing. In F&O we use the BOM Designer with BOM lines and route operations. Phantom BOMs (Reflex's assembly items) map to D365 phantom BOMs or are exploded into the parent BOM depending on the agreed configuration. BOM costing versions are linked to the item costing method migrated in the Item step. Multi-level BOM nesting (BOM referencing BOM) is preserved but flagged for admin validation of route step quantities.

Reflex Projects are cost-tracking entities with project headers, budget lines, actuals, and change orders. We extract project headers with project number, name, status, and all budget-versus-actual lines. In D365 BC we create Jobs with work breakdown structure lines; in F&O we create Projects under Project Management and Accounting. Cost categories from Reflex budget lines are documented for admin to configure cost category posting groups in D365. Change orders migrate as project quotation lines or journal lines depending on their status in Reflex. The budget-versus-actual report structure does not map directly; we preserve actual costs as project journal lines and note that the admin rebuilds the budget reporting layout in D365 Power BI or the native Project statements.

Reflex open AP records are linked to vendor IDs with invoice number, invoice date, due date, amount, and payment terms. We extract all open AP records at the agreed cut-off date. In D365 BC we create open Vendor Ledger Entries with the same vendor number, invoice number, due date, and amount; the entry posts as an open invoice in the AP module. In F&O we use the VendOpenTransMark table. Paid invoices from Reflex are not migrated as open; they are included in a historical AP aging report delivered to the customer for archive. Credit memos and prepayments are handled as separate document types with their own posting profiles and are flagged for admin to assign the correct D365 vendor ledger entry type.

Reflex open AR records are linked to customer IDs with invoice, amount, due date, and aging bucket flags. We extract open AR at cut-off and map to D365 BC Customer Ledger Entries or F&O CustOpenTransMark. Aging bucket assignments from Reflex are preserved in custom fields or dimensions so the customer can reconcile the D365 aging report against Reflex post-migration. Credit memos and prepayments require special handling: unapplied credit memos become open credit memos in D365 AR; prepayments are posted as customer ledger entries with a prepayment flag. Historical closed AR is not migrated as open; it is delivered as a closed AR aging report.

Reflex Fixed Asset records include acquisition date, acquisition cost, depreciation method (straight-line, declining balance, units of production), accumulated depreciation, useful life, and location. We extract the full asset register and map to D365 BC Fixed Assets or F&O Fixed Asset module. Depreciation method from Reflex maps to the D365 depreciation book setup: straight-line maps to Straight-Line, declining balance maps to Declining Balance, and any units-of-production method maps to a custom depreciation convention flagged for admin configuration. Accumulated depreciation carries as the asset's accumulated depreciation balance at cut-off; the net book value is validated against D365's computed balance post-migration. Asset numbers are preserved as D365 asset numbers for depreciation schedule continuity.

Reflex Work Orders link Items, BOMs, and labor routing with status, scheduled dates, and material/labor consumption. We extract open and completed Work Orders with their item, quantity, BOM version, and labor hours. In D365 BC with the Manufacturing module enabled, work orders map to Production Orders with the same item number and quantity; the BOM version is resolved from the BOM migration step. In F&O, production orders use the same structure with additional scheduling and costing integration. Completed work orders that affected COGS and inventory simultaneously are flagged: the inventory impact (finished goods posting) migrates separately from the COGS posting, and the admin validates the cost impact in D365's inventory settlement process post-migration.

Reflex's Document Manager stores binary file attachments linked to transactions and master records. We flag every document association during extraction by recording the parent record type, parent record ID, document filename, and file type. Binary file content is outside standard migration scope; we deliver a document map listing every attachment with its source record reference and recommended target location in D365 (SharePoint for BC, Azure Blob or SharePoint for F&O). The customer configures the SharePoint or Azure Blob integration in D365 before migration, then uses the document map to manually re-attach or bulk-upload files post-migration.

Reflex user records include name, email, role assignments, and the Full Client Access License flag. We extract all user records with their assigned roles. Permission sets in Reflex are platform-specific and cannot be directly mapped to D365's Role-Based Security model. We create D365 User accounts matched by email (for Azure AD synchronization) and deliver a written role-mapping matrix that maps each Reflex role to the nearest D365 security role, duty, and privilege combination. The customer provisions users and assigns roles in D365 before or during the sandbox phase. Minimum user license requirements are validated against the destination D365 edition.

Reflex tax codes define jurisdiction (GST, HST by province, PST by province) and rate for sales and purchase transactions. We extract all active tax codes with their rates and jurisdictions. In D365 BC we create Tax Groups and map each Reflex tax code to a Tax Group with the corresponding Tax Group line; Tax Posting Setup maps Tax Group plus Product Tax Group combinations to the correct general ledger posting accounts. In F&O we create Sales Tax Codes with the same jurisdictions and rates. Nexus-specific tax codes and multi-jurisdiction setups require admin validation post-migration. Canadian provincial tax rates are pre-configured where D365 provides them; custom or expired rates are flagged for manual verification.