Migrate from Falcon ERP to Microsoft Dynamics 365 Business Central

Falcon ERP's hierarchical COA with account types and currency assignments exports to CSV by running the Account List report. We map each account code, name, and type to D365 G/L Account with Account Type (Posting, Heading, Total, Statistics), Direct Posting validation, and the currency assignment per account. GCC multi-currency accounts map to D365's currency-per-account configuration. If Falcon ERP uses segment codes for cost center or department, we map those to D365 dimensions (Business Central Dimensions or F&O Financial Dimensions) rather than as part of the account code.

Falcon ERP Customer records with billing address, credit limit, payment terms, and AR terms map to D365 Customer. The Customer Number from Falcon ERP becomes the D365 Customer Number as a dedupe key. We map AR payment terms to D365 Payment Terms, credit limit to Credit Limit, and the customer price group to a D365 Customer Price Group. Address records export from the Falcon ERP Customer report and map to D365 postal addresses with Address Type (Invoice, Delivery). GCC-specific fields such as CR number map to a custom field on Customer.

Falcon ERP Vendor records mirror the Customer structure with additional WHT (Withholding Tax) codes required for GCC compliance. We map WHT groups from Falcon ERP to D365 WHT Product Posting Groups and WHT Tax Groups, which are required for Saudi and UAE withholding tax reporting. Vendor payment terms map to D365 Payment Terms. The Falcon ERP vendor number becomes the D365 Vendor Number as the dedupe key.

Falcon ERP Items with product/service classification, cost, price, inventory tracking flags, and stock levels by warehouse map to D365 Items. We distinguish between Stockkeeping Items (with inventory tracking) and Services based on Falcon ERP's item type flag. Unit of Measure from Falcon ERP maps to D365 Unit of Measure. Standard Cost and Unit Price migrate to the respective D365 price fields. For items with multi-location stock, we map each warehouse location to a D365 Location code.

Outstanding invoices, credit notes, and partial payments export from Falcon ERP's AR Aging report. We map each open AR record to a D365 Customer Ledger Entry with Remaining Amount, Due Date, and Document No. preserved. Falcon ERP invoice numbers become D365 External Document No. for traceability. Aging buckets are reconstructed from the Due Date and Remaining Amount in D365's Customer Ledger Entry aging view.

Outstanding vendor invoices, credit notes, and payment schedules export from Falcon ERP's AP Aging report. We map each open AP record to a D365 Vendor Ledger Entry with Remaining Amount, Due Date, and Document No. preserved. WHT deductions from Falcon ERP vendor transactions map to D365 WHT Tax Transaction entries linked to the vendor ledger. External Document No. from Falcon ERP carries forward for vendor reconciliation.

Past invoices, payments, receipts, and credit notes export from Falcon ERP's transaction history reports. We export two to three years of history based on the customer's tax audit retention requirements and map line items to D365 General Journal Lines. Each journal batch is tagged with a source identifier and posting date. Document numbers from Falcon ERP become D365 External Document No. References. We validate total debit and credit per journal batch against the Falcon ERP GL trial balance before posting.

Manual and recurring journal entries stored in Falcon ERP export with account references, amounts, and descriptions. We map posted journals to D365 General Journal batches, preserving the journal name (source module), posting date, and line descriptions. Recurring journals are noted separately in the migration handoff document for the customer to rebuild using D365's Recurring Journals feature.

Fixed Asset records from Falcon ERP include acquisition cost, acquisition date, depreciation method, useful life, and accumulated depreciation. We map these to D365 Fixed Asset with the Fixed Asset Group (mapped from Falcon ERP asset category), Depreciation Book, and Ledger Accounts for acquisition and depreciation. Accumulated depreciation maps to a separate FA Ledger Entry with depreciation posting date. We recalculate remaining depreciation schedule in D365 from the current net book value to ensure no duplicate depreciation postings occur post-migration.

Falcon ERP Employee records with personal details, department, job title, employment status, and employment start date map to D365 Worker. We map Falcon ERP department names to D365 Departments and job titles to D365 Positions. Effective-dated employment changes migrate as Worker Employment History entries. National ID and GCC-specific identification fields map to custom fields on Worker if not available in the standard D365 schema.

Payroll history from Falcon ERP includes salary, deductions, allowances, and tax deductions per pay period. We export payroll registers and map pay components to D365 Earning Codes and Deduction Codes. WHT deductions per employee carry forward as D365 Payroll Tax Deductions. Note that D365 Payroll is a separate licensed add-in in Business Central; we map the payroll data to the appropriate D365 Payroll tables and flag any pay components that require configuration in the destination before loading. We do not configure D365 Payroll tax tables as part of the migration scope.

VAT returns and ZATCA Phase 2 e-invoice records from Falcon ERP contain GCC-specific tax codes and e-invoice reference UUIDs. We export tax transactions and map VAT amounts to D365 Tax Transaction entries linked to the corresponding sales and purchase ledger entries. ZATCA Phase 2 e-invoice UUIDs are preserved in a custom field on the related invoice document (D365 Sales Invoice or Purchase Invoice) as zata_uuid__c to maintain audit continuity for Saudi Arabian compliance requirements. GCC VAT rate codes (5% standard, 0% exempt, reverse charge) require a mapping table built during scoping against D365's Tax Group and Tax Product Posting Group configuration.

Bank accounts and cash ledgers from Falcon ERP export from the Account List with bank reconciliation data. We map bank accounts to D365 Bank Account with IBAN, SWIFT/BIC, and Bank Account Number fields. GL balances reconcile against the Falcon ERP trial balance at the bank account level. Bank reconciliation data (cleared transactions and statement lines) does not migrate; the customer starts bank reconciliation in D365 from the go-live date.

Bill of Materials from Falcon ERP define product recipes with component items, quantities, and unit of measure. We map each BOM header and line to D365 Production BOM with item numbers resolved from the Items mapping. BOM Version handling in D365 requires a separate BOM version record if the customer uses version-controlled recipes. The Routing No. field maps to a D365 Routing if the BOM includes operations sequencing.

Open and historical work orders from Falcon ERP map to D365 Production Order. We map item number, quantity, and status (Released, Finished) from Falcon ERP to D365 ProdStatus. Scheduled start and end dates migrate to the Production Order schedule. We do not migrate estimated labor hours or machine hours as D365 calculates these from the attached Routing; the customer validates routing times post-migration.