Migrate from TechnologyOne to Infor CloudSuite Corporate

TechnologyOne Financials stores the full account hierarchy with account codes, classifications, and balance mappings extractable via the Business View API or direct dataset access. Infor CloudSuite Financials uses multi-segment chart of accounts structures with configurable account code masks per business entity. We map TechnologyOne account codes to Infor segment values, preserving account type (asset, liability, equity, revenue, expense), balance type, and posting controls. Fiscal period mapping is required because TechnologyOne and Infor use different period close statuses and period date ranges.

Customer master records from TechnologyOne Financials map to Infor Customer records with contact details, payment terms, credit limits, and any custom fields added to the customer record. We transform payment term codes (TechnologyOne's internal format to Infor's terms table) and preserve credit limit values as Infor credit ceiling fields. Customer type (council, education, commercial) maps to Infor's customer classification if the destination uses industry-specific configurations.

Supplier records from TechnologyOne Financials map to Infor Supplier records with address details, payment terms, bank account information, and any custom fields on the supplier record. We handle supplier tax registration numbers and ABN/Australian Business Number fields by mapping to Infor's tax ID fields. Where TechnologyOne stores supplier contract terms, we preserve those in Infor's supplier notes field or map to a contract management module if included in the destination scope.

Accounts payable records with payment arrangements, direct debits, and bulk transaction histories require careful sequencing to avoid triggering duplicate payment runs during import. We extract open invoice records with invoice number, supplier reference, invoice date, due date, amount, and line distribution. Infor AP invoice import requires the supplier record to exist first (parent lookup resolution). Payment runs and scheduled payment arrangements are mapped as separate payment records or payment schedule entries in Infor.

Accounts receivable records including debtor invoices, payment receipts, credit notes, and payment arrangement schedules migrate to Infor AR. We sequence open item migration to avoid reprocessing triggers that could create duplicate debtor statements. TechnologyOne's bulk transaction histories (batch payment imports) map to Infor cash receipt batches. Invoice aging data is preserved as a custom field set for reconciliation after load.

HR and payroll records including compensation history, job titles, department assignments, and employment status migrate from TechnologyOne HR module. Effective-dated changes require sequencing to preserve history in Infor HCM's position and assignment model. TechnologyOne stores pay grades and award classifications that we map to Infor's job classification structure. Where TechnologyOne uses custom HR fields, we discover them during the discovery phase and map each to Infor HCM custom fields.

Asset registers with acquisition dates, asset classifications, depreciation schedules, and current book values migrate from TechnologyOne Assets module API to Infor CloudSuite Asset Management. Depreciation methods (straight-line, diminishing value, units of production) require value-mapping transformation because the method codes differ between systems. Useful life values and residual values transfer directly. Asset location and custodian assignments map to Infor asset assignment records.

Purchase orders and purchase requisitions in TechnologyOne's procurement module are queryable via the Business View API. We map PO header fields (PO number, supplier, order date, delivery date) and line items (item number, description, quantity, unit price, line total) to Infor Procurement. Workflow states and approval histories require mapping to Infor's approval workflow configuration, which must be rebuilt by the customer's admin post-migration.

TechnologyOne ECM stores documents, document sets, compound documents, and custom document fields via the EzeScan CMIS-compatible connector. We extract document metadata and file references; the physical files transfer via secure file transfer to Infor Document Management. Custom document fields require pre-migration field discovery because there is no self-documenting schema endpoint. We query EzeScan or the dataset directly for all custom field definitions and map each to Infor document property fields. Any missed custom fields result in blank values in Infor.

Property and Rating module records apply only to local government TechnologyOne customers running OneCouncil. Assessments, charge runs, and fee schedules are extractable but the billing engine uses custom calculation rules that require transformation mapping. We extract the property register, assessment records, and charge schedules and map them to Infor CloudSuite Public Sector equivalents if that module is included in the destination scope. Where custom billing rules exist, we document the rule logic for manual recreation in Infor rather than attempting automated transformation.

TechnologyOne stores custom fields added to any standard object within the isolated dataset, but there is no unified custom field registry. We discover all custom fields during the discovery phase by querying the dataset or reviewing module configurations, then map each one individually to the corresponding Infor custom field. We flag any custom fields that have no Infor equivalent and document them for the customer's admin to configure post-migration.