Migrate your Unit4 ERP data

Unit4's Customer entity holds billing and delivery addresses, payment terms, and tax registration. We map Customer records 1:1 into the destination schema, preserving credit limits and any custom fields added via the custom-field framework.

Supplier master data includes bank details, W-9/W-8 status, and multi-address support. We transfer Supplier records with their associated tax and payment configuration intact.

Unit4 supports multidimensional account structures with cost centres, departments, and projects as natural axes. We flatten these into the destination's account hierarchy, discussing whether to preserve the dimensional tagging or collapse it into flat account codes.

Items include GL mapping, cost price, sales price, and stock control flags. Unit4 allows complex pricing matrices that the destination may represent differently—we align on a per-item mapping strategy during scoping.

General Ledger accounts with account type, posting controls, and currency settings are well-structured in Unit4. We migrate account codes, descriptions, and posting rules directly.

Outstanding invoices, credit memos, and payment applications carry forward as open records. We map document headers and line items, preserving due dates, amounts, and currency.

Unit4 stores years of journal history in relational tables. Bulk extraction requires SQL access or GCON4 MFL. We scope the date range and decide whether to migrate full history or a configured window based on the destination's capacity.

Posted journal entries with header, lines, and audit stamps transfer as locked records. We preserve posting dates, source references, and user stamps to maintain audit trails in the destination system.

Unit4 holds country-specific tax matrices with rates, jurisdictions, and posting rules. We map these to destination tax codes, flagging any jurisdiction combinations that require manual review.

Asset master records include depreciation schedules, cost centres, and insurance values. Unit4 and the destination may use different depreciation methods—we align on a conversion approach per asset category.

Unit4 stores document attachments against transactions and master records. We extract these via the document management API and re-associate them in the destination, noting that file-size and format restrictions apply.

Bank account masters with currency, account type, and reconciliation settings migrate directly. We map opening balances and reconcile them post-migration.

Unit4 HCM holds employment history, compensation, job titles, and department assignments. Employee records may carry effective-dated changes that require careful sequencing in the destination's HR schema.

Projects in Unit4 are the primary work-identification layer, with WBS elements, cost objects, billing rates, and resource assignments. Project structures are heavily customer-configured and require a detailed mapping review before migration.

Unit4's grant management module handles donor restrictions, fund balances, and reporting for nonprofits and public-sector bodies. We map grant codes, funding allocations, and spend-vs-budget records, noting that downstream reporting requirements shape the field mapping.