Migrate from Solution ERP to Infor CloudSuite Corporate

Account codes, names, and hierarchies transfer with mapping to the destination Infor legal entity's chart. Gulf-specific VAT and excise tax codes require explicit translation because Solution ERP's Qatar tax catalogue does not have direct Infor equivalents. We extract the full tax code catalogue during discovery, build a mapping table to Infor's tax configuration, and flag codes without an equivalent for the customer's finance team to resolve before import. Active and inactive account flags transfer; inactive accounts are created in Infor but marked inactive to preserve audit continuity.

Customer master records including Arabic company names, contact details, addresses, and payment terms transfer. Arabic UTF-8 encoding is preserved, and we verify the destination Cloudsuite edition supports RTL field rendering. Tax registration numbers and credit limits map to Infor's customer tax and credit configuration. We resolve the Customer's legal entity assignment during scoping based on the customer's operating entity structure.

Vendor master records including tax registration numbers, IBAN bank details, and payment terms transfer. We validate IBAN and bank account formats against the destination country's banking standards and flag any records with format mismatches. Vendor tax codes map to the Infor supplier tax configuration using the same tax translation table built for the Chart of Accounts. Vendors are loaded before AP records so that supplier references are satisfied at insertion.

Item records with pricing, stock levels, and unit-of-measure hierarchies require unit-of-measure mapping between Solution ERP's naming conventions and Infor's unit-of-measure standards. Item cost and standard price fields transfer to Infor's cost and price structure. We flag items with missing unit-of-measure assignments during discovery and quarantine them for manual resolution before the item import batch runs.

Project records including budgets, milestones, phases, cost allocations, and billing schedules transfer directly to Infor CloudSuite's project module. Construction-specific phases and billing schedules map to Infor project phases and billing rules. Solution ERP cost-centre codes map to Infor department IDs, and we preserve the mapping in a cross-reference table for the customer's project team to validate post-migration. Project status, percent complete, and earned-value metrics transfer where the source fields are populated.

Outstanding payables require careful date-range scoping to prevent duplication. We match open invoice numbers against Infor's AP register using the supplier reference, invoice number, and invoice date as a composite dedupe key. Partial payments spanning the migration cutoff date are flagged and held for the customer's AP team to reconcile manually after cutover. We apply a migration-date balance adjustment to the supplier account for any transactions posted between the export snapshot and the cutover date.

Outstanding receivables are scoped, deduplicated, and loaded in the same manner as AP. We match open invoice numbers to Infor's AR register using customer reference, invoice number, and invoice date. Partial payments and credit memos spanning the cutoff date are flagged and held for manual reconciliation. Aged trial balance figures are preserved as of the migration date to support the customer's finance team in verifying the opening balance in Infor.

Historical journal entries transfer on request with full line-item detail including posting date, period, account code, debit, credit, and description. Volume-based chunking applies for histories exceeding 50,000 lines; we chunk by fiscal year and load in sequence to preserve period continuity. Original posting dates and periods are preserved to maintain audit continuity. We flag duplicate entries identified through composite key matching (account, date, amount, description) for the customer's finance team to confirm before finalising the import.

Attached files and document metadata (date, author, type, description) require file-type filtering because binary document storage models differ between Solution ERP and Infor CloudSuite. We extract document metadata separately from binary content, map metadata to Infor's document management fields, and flag any records with unsupported file types. Binary document migration to Infor Document Management requires a separate file transfer process coordinated with the customer's Infor implementation team.

Bank account balances and cash account records transfer with a migration-date cutoff balance adjustment. We reconcile any transactions posted between the export snapshot and the cutover date against the account balance to produce an adjusted opening balance for Infor. We preserve the original bank account code from Solution ERP as a reference field in Infor to support the customer's finance team in tracing historical transactions.

Asset registers including acquisition dates, depreciation methods, useful life, and net book value transfer to Infor's fixed asset module. We validate depreciation schedules against the destination's tax depreciation rules and flag any assets with depreciation methods not supported in Infor. Partially depreciated assets transfer with accumulated depreciation and NBV preserved to support the customer's fixed asset register continuity.

User accounts and role assignments transfer as role-name mappings because permission structures vary between Solution ERP and Infor CloudSuite. We flag admin-level accounts and accounts with custom permission sets for explicit review by the customer's Infor system administrator. The destination Infor tenant's user provisioning is coordinated with the Infor implementation team because Infor CloudSuite user management runs through the Infor OS identity layer.