Migrate your TechnologyOne data
Monolithic SaaS ERP built for government, education, and asset-intensive industries in ANZ. The CiA platform runs single-tenanted databases under a shared application layer, making data extraction and re-platforming a structurally complex undertaking.
In its favor
Why people choose TechnologyOne
The signal that keeps TechnologyOne on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Most customers are long-term TechnologyOne users who upgraded from the on-premise CI release to CiA, so the platform has deep institutional knowledge in government finance and asset management workflows.
The bundled suite model means organisations already have financials, HR, and asset management under one vendor umbrella, reducing multi-vendor complexity for mid-market councils and universities.
TechnologyOne holds strong positions in local government and education verticals in Australia and New Zealand, so customers in these sectors choose it for pre-built compliance templates and sector-specific reporting.
The SaaS+ model promises faster implementation timelines, with TechnologyOne advertising ERP deployment within 30 days for some configurations, attracting organisations with constrained change-management capacity.
Built-in sector solutions like OneCouncil, OneEducation, and OneGovernment reduce configuration overhead for councils and school systems that do not need custom ERP architecture.
Customers report that the user interface, particularly the CI legacy interface, feels dated compared to modern SaaS ERP alternatives, driving preference for cleaner UX platforms like NetSuite or Workday.
The monolithic bundled model means organisations pay for modules they may not use; customers seeking modular per-user or per-transaction pricing find the model inflexible and costly at scale.
Limited public API documentation and a historically API-light architecture make integrations with modern third-party tools difficult, pushing technical teams toward more open platforms.
Gartner Peer Insights scores are modest at 3.6 stars with a small review pool, indicating lower customer satisfaction and advocacy compared to competitors in the ERP space.
Upgrade cycles from CI to CiA have required significant consulting effort and custom role rebuilding, creating churn among customers who want a cleaner migration path.
Reasons to switch
Why people leave TechnologyOne
The recurring reasons buyers give for replacing TechnologyOne. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where TechnologyOne fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
TechnologyOne pricing overview
TechnologyOne does not publish per-user or per-module pricing publicly. The SaaS+ subscription model is enterprise-oriented and typically negotiated based on modules deployed, user count, and organisation size. Competitor intelligence places comparable ERP subscriptions in the mid-to-high range for local government and education customers.
Local Government SaaS+
Tier 1 of 3
From £20,000/year base, modules from £2,500 (UK G-Cloud 13 reference)
What's included
Need help selecting your ERP?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on TechnologyOne's schedule — see our quote-based pricing →
What gets migrated
TechnologyOne object support
Object-by-object support for TechnologyOne migrations. Per-pair details surface during scoping.
Chart of Accounts
Fully supportedThe general ledger structure is well-documented in TechnologyOne Financials. We extract the full account hierarchy, account codes, and balance mappings via the Business View API or direct dataset access. Account types and currency settings are preserved 1:1.
Customers and Suppliers
Mapping requiredCustomer and supplier master records live in the financials module. We map contact details, payment terms, and credit limits. Custom fields added to supplier or customer records may require field-level mapping depending on the destination schema.
Open AP and AR Records
Mapping requiredAccounts payable and receivable with payment arrangements, direct debits, and prepayments are supported. We sequence open items carefully to avoid triggering duplicate payment runs during import. Historical transactions require separate historical ledger migration scope.
Employees
Mapping requiredHR and payroll records including compensation history, job titles, and department assignments are stored in the HR module. Effective-dated changes require careful sequencing to preserve history in the destination system.
Fixed Assets
Mapping requiredAsset registers with depreciation schedules, acquisition dates, and asset classifications migrate via the Assets module API. Depreciation methods may differ between systems and require value-mapping at import time.
Documents and ECM Records
Mapping requiredTechnologyOne ECM stores documents, document sets, compound documents, and custom document fields. The EzeScan connector uses CMIS-compatible endpoints. We extract document metadata and relationships; binary file extraction depends on storage configuration in the dataset.
Procurement Records
Mapping requiredPurchase orders, purchase requisitions, and receipt records in the procurement module are queryable via the Business View API. Workflow states and approval histories require mapping to destination workflow statuses.
Property and Rating Assessments
Mapping requiredProperty and Rating module is specific to local government customers. Assessments, charge runs, and fee schedules are extractable. The billing engine uses custom calculation rules that require transformation logic during migration.
Custom Properties
Mapping requiredCustom fields added to any standard object are stored in the dataset. There is no unified custom field registry — we discover them during the discovery phase and map each one individually to the destination.
Users and Roles
Not in this platformUser accounts and role-based security profiles are tied to TechnologyOne's internal identity layer and the CiA role/user interface configuration. We do not migrate user accounts because these must be recreated in the destination with appropriate permissions.
| Object | Support | Notes |
|---|---|---|
| Chart of Accounts | Fully supported | The general ledger structure is well-documented in TechnologyOne Financials. We extract the full account hierarchy, account codes, and balance mappings via the Business View API or direct dataset access. Account types and currency settings are preserved 1:1. |
| Customers and Suppliers | Mapping required | Customer and supplier master records live in the financials module. We map contact details, payment terms, and credit limits. Custom fields added to supplier or customer records may require field-level mapping depending on the destination schema. |
| Open AP and AR Records | Mapping required | Accounts payable and receivable with payment arrangements, direct debits, and prepayments are supported. We sequence open items carefully to avoid triggering duplicate payment runs during import. Historical transactions require separate historical ledger migration scope. |
| Employees | Mapping required | HR and payroll records including compensation history, job titles, and department assignments are stored in the HR module. Effective-dated changes require careful sequencing to preserve history in the destination system. |
| Fixed Assets | Mapping required | Asset registers with depreciation schedules, acquisition dates, and asset classifications migrate via the Assets module API. Depreciation methods may differ between systems and require value-mapping at import time. |
| Documents and ECM Records | Mapping required | TechnologyOne ECM stores documents, document sets, compound documents, and custom document fields. The EzeScan connector uses CMIS-compatible endpoints. We extract document metadata and relationships; binary file extraction depends on storage configuration in the dataset. |
| Procurement Records | Mapping required | Purchase orders, purchase requisitions, and receipt records in the procurement module are queryable via the Business View API. Workflow states and approval histories require mapping to destination workflow statuses. |
| Property and Rating Assessments | Mapping required | Property and Rating module is specific to local government customers. Assessments, charge runs, and fee schedules are extractable. The billing engine uses custom calculation rules that require transformation logic during migration. |
| Custom Properties | Mapping required | Custom fields added to any standard object are stored in the dataset. There is no unified custom field registry — we discover them during the discovery phase and map each one individually to the destination. |
| Users and Roles | Not in this platform | User accounts and role-based security profiles are tied to TechnologyOne's internal identity layer and the CiA role/user interface configuration. We do not migrate user accounts because these must be recreated in the destination with appropriate permissions. |
Gotchas
What to watch for in TechnologyOne migrations
Issues we've hit on past TechnologyOne migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
CI-to-CiA hybrid environments complicate data scoping
Single-tenanted dataset requires direct database access
Custom document fields in ECM require manual discovery
XlOne and custom financial reports do not auto-migrate
| Severity | Issue |
|---|---|
| High | CI-to-CiA hybrid environments complicate data scoping |
| High | Single-tenanted dataset requires direct database access |
| Medium | Custom document fields in ECM require manual discovery |
| Medium | XlOne and custom financial reports do not auto-migrate |
Leaving TechnologyOne?
Where TechnologyOne customers move next
6 destinations TechnologyOne can migrate to.
How a TechnologyOne migration works
Four steps, TechnologyOne-specific
Connect
OAuth-based authentication for the Business View API and Data Model API on the CiA platform; specific scope and token mechanics are provided to customers under the SaaS+ agreement rather than via a public developer portal. into TechnologyOne. Scopes limited to read-only on the data we move.
Map
We translate TechnologyOne-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate TechnologyOne quirks before production.
Migrate
Full migration with TechnologyOne rate-limit handling. Rollback available throughout.
FAQ
TechnologyOne migration FAQ
Answers to the questions buyers ask most during TechnologyOne migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your TechnologyOne migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate TechnologyOne.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your TechnologyOne setup and destination — written quote back within a business day.