Migrate from Falcon ERP to Infor CloudSuite Corporate

Falcon ERP stores a hierarchical Chart of Accounts with account types (Asset, Liability, Equity, Revenue, Expense) and currency assignments. We export account codes, names, types, and currency flags to CSV, then map each to Infor CloudSuite's COA structure via the Import Rule Definition form. Falcon ERP's internal account code format (which may include segment prefixes for cost centers) is normalized to Infor CloudSuite's account code length and segment configuration during the transform step. Multi-segment COA configurations (if Falcon ERP uses Business Unit or Department segments) are preserved as Infor CloudSuite account segments.

Falcon ERP customer records include billing address, credit limit, payment terms, and AR balance. We export all customer fields to CSV, map to Infor CloudSuite Customer, and resolve the AR terms and credit limit configuration. Falcon ERP's customer-specific tax registration numbers (TRN for UAE VAT, VAT number for Saudi) are stored in Infor CloudSuite's Tax Registration fields. Customer balances are verified against Falcon ERP's AR aging report before the Infor load to catch any truncation in the spreadsheet export.

Falcon ERP vendor records parallel customer records with AP terms and withholding tax (WHT) codes required for GCC compliance. We export vendors and map to Infor CloudSuite Supplier, preserving WHT configuration flags. Falcon ERP's vendor-specific tax registration and CR number fields map to Infor CloudSuite's supplier tax registration fields. Separate AP aging reports per vendor are reconciled against the exported vendor balance to ensure no open invoice lines are lost in the spreadsheet export.

Items include product/service classification, cost, price, inventory tracking flags, and stock levels by warehouse location. We export items with stock levels per location and map to Infor CloudSuite Item Master, preserving unit of measure, cost layer method (FIFO or Standard), and inventory tracking flags. Falcon ERP's item-specific tax codes (VAT rate assignments) are mapped to Infor CloudSuite's tax attribute on item. For manufactured items with BOMs, the item record flags the routing link to manufacturing.

Outstanding invoices, credit notes, and payment schedules are exported per customer and vendor. We map open balances to Infor CloudSuite's AR/AP register, preserving aging buckets (Current, 30-60-90+ days), due dates, and invoice reference numbers. Falcon ERP's ZATCA e-invoice UUID embedded in each open invoice is preserved in a custom field (zakatca_uuid__c) on the Infor CloudSuite AR/AP record to maintain Saudi VAT audit trail continuity. Open invoice counts are reconciled to the penny against Falcon ERP's trial balance before the Infor load is committed.

Past invoices, payments, receipts, and credit notes spanning 2-3 years of history are exportable to spreadsheet from Falcon ERP's reporting module. We export transaction headers and line items separately, then map to Infor CloudSuite Journal Entry records with account references, debit/credit amounts, and transaction dates preserved. Falcon ERP's journal entry numbering scheme is stored in a custom reference field on each Infor CloudSuite journal line. Historical transactions are loaded after the COA is validated to ensure all account codes exist in the destination.

Manual and recurring journal entries stored in Falcon ERP are exported with account references, amounts, and posting dates. We map to Infor CloudSuite Journal Entry, preserving the original journal number and description. Recurring journal entries (standing journals) are documented separately in the automation inventory for the customer's admin to rebuild in Infor CloudSuite's Recurring Journal template if required.

Fixed asset records include acquisition cost, acquisition date, depreciation method (straight-line or reducing balance), useful life, salvage value, and accumulated depreciation to date. We export the asset register from Falcon ERP and map to Infor CloudSuite Fixed Assets, recalculating remaining depreciation schedules on load using Infor CloudSuite's depreciation engine. Falcon ERP's asset tag numbers map to Infor CloudSuite's Asset ID field. Any fully depreciated assets are flagged for review before load to prevent unexpected depreciation entries.

Employee records include personal details (name, ID, nationality, join date), department, job title, employment status, and reporting manager. We export all employee data and map to Infor CloudSuite HCM Employee, preserving effective-dated changes where Falcon ERP tracks history. Falcon ERP's employee-specific WHT configuration flags migrate to Infor CloudSuite's employee tax profile. Active and inactive employee records are loaded together to preserve headcount history; inactive status is set on the Infor record to match Falcon ERP's employment_status field.

Payroll history includes salary components, allowances, deductions, and tax deductions per pay period. We export payroll registers from Falcon ERP and map to Infor CloudSuite Payroll, preserving pay components (Basic, Housing, Transport, Commissions), deduction types (loan repayments, benefits), and WHT deductions. Each pay period is loaded as a separate payroll run with employee-level detail. Falcon ERP's salary advance and loan balance records are mapped to Infor CloudSuite's employee advance and loan modules with remaining balance recalculated on load.

VAT returns and ZATCA e-invoice records contain GCC-specific tax codes and e-invoice reference numbers. We export tax transactions and build a VAT mapping table during scoping that cross-references Falcon ERP's internal tax codes against Infor CloudSuite's tax configuration. ZATCA Phase 2 UUIDs from Falcon ERP's e-invoice records are preserved in a custom field on each Infor CloudSuite AR/AP record or journal entry for audit continuity. Where no tax code match exists, we flag the discrepancy and create new tax codes in Infor CloudSuite before loading any financial transactions.

Bill of Materials and work orders define product recipes, component quantities, and production steps. We export BOM structures (parent item, components, quantities per, Phantom BOM flags) and open work orders from Falcon ERP, then map to Infor CloudSuite Industrial's BOM and Work Order modules. BOM routing steps (operations, work centers, machine hours) are mapped to Infor CloudSuite's routing configuration. Work order status (Released, In-Process, Completed, Closed) is preserved, with any partially completed work orders flagged for review before load to prevent inventory inconsistency in Infor CloudSuite.