Migrate from Unit4 ERP to Infor CloudSuite Corporate

Unit4 Customer records—holding billing and delivery addresses, payment terms, and tax registration—map directly to Infor CloudSuite Customer (Party type = Customer). We preserve credit limits in the Infor credit-hold fields and map any Unit4 custom address extensions to Infor country-specific address structures. Customer accounts must be imported before any open AR documents because document-to-customer foreign keys must resolve at insert time.

Unit4 Supplier master data including bank details, W-9/W-8 status, and multi-address support transfers to Infor CloudSuite Supplier records. Tax registration numbers map to Infor tax registration fields per jurisdiction. Supplier records import before open AP documents to satisfy the vendor foreign key on invoice headers.

Unit4's multidimensional account structures with cost-centre, department, and project as natural posting axes require flattening for Infor CloudSuite's GL. We map Unit4 account segments to Infor account code segments in the COA structure, and assign Unit4 cost-centre and department values to Infor cost-object definitions (or to Infor WBS elements for project-linked accounts). The customer chooses whether to preserve the full segment structure as Infor account subledgers or to aggregate into a flattened chart with cost-object tracking handled separately in project modules.

Unit4 GL Account codes, descriptions, account types, posting controls, and currency settings migrate to Infor CloudSuite Account Code records. Account type determines the Infor posting-group assignment. We preserve any user-defined account number formats and map posting-rule restrictions to Infor account-control settings. Currency settings on accounts are honoured for multi-currency organisations.

Posted journal entries from Unit4 transfer to Infor CloudSuite GL Journal records with header, lines, and audit stamps. We preserve posting dates, source references, user stamps, and any batch-identification fields to maintain audit trails. Locked journal status in Unit4 translates to a posted-and-protected flag in Infor that prevents post-migration editing.

Outstanding AP invoices, credit memos, and payment applications carry forward as open AP records in Infor CloudSuite. We map document headers and line items, preserving due dates, amounts, currency, and discount terms. Vendor references are resolved to the Supplier records imported in the prior phase. Infor requires invoice and payment records to be imported in a specific sequence due to document-numbering dependencies.

Outstanding AR invoices, credit memos, and payment applications transfer to Infor CloudSuite AR records. Customer references are resolved to Customer records from the master data phase. Invoice and payment sequences in Infor must be respected to maintain document-numbering integrity. Partial payments and credit allocations are preserved at the line-item level.

Unit4's country-specific tax matrices with rates, jurisdictions, and posting rules map to Infor CloudSuite tax codes and jurisdiction assignments. We flag any jurisdiction combinations that have no direct Infor equivalent—for example, EU VAT regimes with specific reverse-charge conditions that require a manual tax-code setup in Infor. The customer's Infor consultant reviews and approves all tax-code mappings before the ledger phase begins.

Unit4 Asset master records include depreciation schedules, cost-centre assignments, and insurance values. Unit4 and Infor CloudSuite use different default depreciation methods—straight-line versus declining-balance—so we align on a conversion approach per asset category. Depreciation already calculated in Unit4 is preserved as a cumulative accumulated-depreciation figure in Infor at the cutover date, with future depreciation recalculated from Infor's schedule going forward.

Unit4 Projects with WBS elements, cost objects, billing rates, and resource assignments map to Infor CloudSuite Project records with WBS elements. Project structures in Unit4 are heavily customer-configured—we extract the full WBS hierarchy, map cost-object assignments to Infor cost-object codes, and preserve billing-rate tables per project. If Unit4 project milestones carry milestone-type billing events, these map to Infor project billing milestones. Projects must be imported after the Chart of Accounts and before any project-linked journal entries.

Unit4's grant management module handles donor restrictions, fund balances, and spend-vs-budget reporting for nonprofits and public-sector bodies. We map grant codes, funding allocations, and spend-vs-budget records to Infor CloudSuite Grant or Fund Code structures. Donor-restriction flags transfer as grant attribute fields. If the destination is CloudSuite Financials without a dedicated grant module, we map fund codes to Infor cost-object segments with a written grant-coding convention for the customer's Infor consultant to implement.

Unit4 HCM holds employment history, compensation, job titles, and department assignments. Employee records carry effective-dated changes (hire date, title changes, salary adjustments) that require careful sequencing in Infor CloudSuite's HR schema. We import current active records as Infor Employee records and preserve historical changes as HR audit entries. If the destination Infor CloudSuite includes Infor HCM, we map to Worker records with employment relationship data; otherwise we map to a custom employee staging object for the customer's HR team to reconcile.