Practical guide to TechnologyOne Ci Anywhere migration, SaaS transition, configuration management, and support for Australian organisations.
IT managers, finance managers, and project leads at organisations running TechnologyOne who need to plan their Ci Anywhere migration or manage ongoing platform support.
What does the Ci Anywhere migration involve, and how do we manage customisations and integrations through the transition?
TechnologyOne is an Australian-developed ERP platform primarily used by government agencies, universities, local councils, health services, and community organisations. It's one of the few ASX-listed enterprise software companies in Australia, and it dominates in sectors where compliance, grants management, and fund accounting are critical.
The company has been in business since 1987, and many organisations have been running TechnologyOne for decades. That longevity means deep functional coverage for its target industries — but also a lot of legacy configurations and customisations in the field.
TechnologyOne is aggressively moving customers to Ci Anywhere, their cloud-hosted SaaS platform. On-premises installations are being phased out. For many organisations, this isn't a choice — it's a scheduled migration.
Forced SaaS migration. TechnologyOne has announced that all customers will move to Ci Anywhere. On-premises support is being wound down version by version. If you haven't started planning, the clock is ticking.
Customisation restrictions. The SaaS model is more restrictive than on-premises. TechnologyOne limits code-level customisation to maintain upgrade reliability. Organisations with heavy customisation need to find alternative approaches.
Release cadence. Ci Anywhere receives regular updates controlled by TechnologyOne. Unlike on-premises where you chose when to upgrade, SaaS updates are applied on TechnologyOne's schedule.
Australian-specific requirements. TechnologyOne handles Australian compliance well (BAS, STP, grant reporting), but changes in government reporting requirements can create gaps that need configuration updates or workarounds.
Ci Anywhere migration. The primary path. Move from on-premises TechnologyOne to the cloud-hosted Ci Anywhere platform. This involves data migration, configuration review, reconfiguration of customisations, integration updates, and user retraining.
Version-to-version upgrade (on-premises). If you're on an older on-premises version, you may need to upgrade to a more recent on-premises version before migrating to Ci Anywhere. TechnologyOne can advise on the recommended migration path.
Integration modernisation. Regardless of migration path, this is the right time to modernise integrations. Move from direct database connections and file-based transfers to TechnologyOne's API layer.
Complementary applications. For functions that TechnologyOne doesn't cover well or where SaaS customisation restrictions limit you, build companion web applications that integrate through APIs.
Configuration vs customisation. In Ci Anywhere, TechnologyOne distinguishes between configuration (supported: workflows, forms, rules, dashboards) and customisation (restricted: code-level changes, database modifications). Understand which of your current customisations are which.
Direct database access. On-premises installations often use direct SQL queries for reporting and integration. In Ci Anywhere, direct database access isn't available. Everything goes through TechnologyOne's APIs and reporting tools.
Integration points. Common integration scenarios for TechnologyOne:
Data migration. Moving data from on-premises to Ci Anywhere requires careful planning, especially for organisations with decades of historical data. Consider what data needs migrating vs archiving.
Ci Anywhere restricts deep customisation. Identify which customisations need alternative solutions.
Direct SQL integrations must be replaced with APIs. Budget for this work.
Confirm where Ci Anywhere data is hosted and whether it meets your compliance requirements.
External reporting tools need new connection methods. Plan for report rebuilds.
Staff accustomed to the on-premises interface will need structured retraining.
Yes — TechnologyOne (often shortened to TechOne) is the official name. The company is ASX-listed as TNE. It's an Australian-developed ERP focused on government, education, health, and community services.
Ci Anywhere is the cloud-hosted, browser-based version of TechnologyOne. The company is actively migrating all customers to SaaS. On-premises installations are being phased out, so if you haven't started your Ci Anywhere migration, it should be on your roadmap.
Typically 6-12 months including planning, configuration review, data migration, user training, and parallel running. Complex environments with heavy customisation or many integrations may take longer.
Custom reports built in older TechnologyOne reporting tools need reviewing. Some translate to the Ci Anywhere reporting framework; others need rebuilding. If you're using external reporting tools (Crystal Reports, SSRS), those connections need re-establishing for the SaaS environment.
TechnologyOne limits customisation in the SaaS model to protect upgrade reliability. Configuration (settings, workflows, forms) is supported; deep code-level customisation is restricted. This means some customisations may need replacing with external applications or middleware.
Tell us what you are comparing, replacing, or trying to improve. We will come back with a practical recommendation and realistic scope.
