Migrate from TechnologyOne to Acumatica

TechnologyOne's segment-coded accounts map to Acumatica GLAccount for the natural account number and Subaccount for each segment value (division, cost centre, department). FlitStack AI parses the TechnologyOne account string and decomposes it into the GLAccount-Subaccount pair defined in the Acumatica subaccount mask.

Direct 1:1 map. TechnologyOne customer fields (name, class, payment terms, credit limit) map to Acumatica Customer fields. Addresses from TechnologyOne location records migrate as CustomerLocation entries linked to the Customer. Primary contact details become the default location contact. Multi-address setups in TechnologyOne split into separate CustomerLocation records in Acumatica with appropriate address types.

Direct 1:1 map. TechnologyOne vendor fields (name, payment terms, tax ID, currency) map to Acumatica Vendor fields. Multiple TechnologyOne vendor addresses migrate as separate VendorLocation records. 1099 flag and payment hold status carry forward as Vendor attributes. Remittance addresses and primary purchase contacts also translate to VendorLocation entries with appropriate designations.

Direct 1:1 map for standard stock items. TechnologyOne item class, stock unit, and valuation method map to Acumatica ItemClass, BaseUnit, and ValuationMethod respectively. Non-stock items use the Non-Stock flag in Acumatica. Lot/serial tracking settings translate to the corresponding Acumatica lot/serial configuration.

TechnologyOne AR transactions map to Acumatica ARInvoice records. Header fields (reference number, date, description) migrate as InvoiceNbr, InvoiceDate, and Description. Line items map to ARTran records linked to the parent invoice, preserving quantity, unit price, and account allocation. Tax amounts, discounts, andFreight charges carry forward as separate line components within the ARInvoice document.

TechnologyOne AP transactions map to Acumatica APInvoice records. Vendor reference and invoice date carry forward. Line allocations map to APTran records with account and subaccount assignments. Prepayments and adjustments translate as separate AP document types in Acumatica. Payment terms and due dates are preserved to maintain vendor relationship continuity in the target system.

TechnologyOne purchase orders migrate to Acumatica POOrder. Header status, vendor, and date map directly. POLine records preserve item reference, quantity ordered, and cost. Drop-ship and fulfilment-set indicators on TechnologyOne lines carry forward as corresponding Acumatica flags. Line hold status and approval workflows on POs do not migrate and must be rebuilt in Acumatica.

TechnologyOne sales orders map to Acumatica SOOrder. Header fields (order number, customer, date) migrate directly. SOLine records preserve item, quantity, and pricing. TechnologyOne hold and approval status translate to the corresponding Acumatica status fields, with a flag note since approval logic is not migratable.

TechnologyOne HR employee records map to Acumatica Employee. Name, department, cost centre, employment type, and compensation fields migrate as Employee attributes. Hire date, termination date, and salary history carry forward as attribute records for payroll continuity in Acumatica Payroll. Active employee status and department assignments are preserved to maintain organizational reporting structures in the target system.

TechnologyOne project or work order records map to Acumatica Project. Project ID, name, status, and customer reference become Project fields. Cost budget lines translate as ProjectTask records with budget amounts per task. Non-projectable work orders without a customer link land as stand-alone Projects.

TechnologyOne asset register entries migrate to Acumatica FixedAsset. Asset tag, description, acquisition date, cost, depreciation method, and accumulated depreciation carry forward as FixedAsset attributes and depreciation schedules. Book values and depreciation calendars are preserved to ensure continuity of financial reporting across the migration boundary. Acumatica's Fixed Asset module must be licensed to receive this data.

TechnologyOne tax zone definitions map to Acumatica TaxZone. Tax rates are mapped value-by-value to TaxCategory entries. Jurisdictional tax codes are translated to Acumatica tax agency setup. Your Acumatica admin reviews and validates all tax mappings before posting live transactions to ensure compliance with local tax regulations in the target jurisdiction.

TechnologyOne extended properties do not have a direct Acumatica equivalent. We map each TechnologyOne custom property to an Acumatica UDF on the matching business object, preserving the original data type (string, number, date, picklist). Your Acumatica admin must pre-create the UDFs before the migration run; we deliver the UDF specification as part of the schema plan.