Xero Ultra changes an important conversation. For years, businesses moving away from Sage 200, Access Dimensions, Business Central, NetSuite and other ERP or legacy systems have been told that Xero is “only for small businesses”. Xero itself is now pushing deliberately into more complex, scaling-business territory.
What is Xero Ultra?
Xero Ultra is Xero's most advanced plan, launched in Australia in July 2026 for growing and medium-sized businesses managing greater financial complexity. Xero describes the proposition around stronger financial control, sophisticated reporting, more entities, more transactions and better visibility, without automatically taking on the cost and implementation burden of a traditional ERP.
That positioning matters. Ultra is not simply a bigger bundle of familiar subscription features. It is a signal about the type of organisation Xero wants the platform to support.
The Australian plan gives that positioning some substance. Xero Central lists Syft Advanced, priority support and targeted data restores as Ultra inclusions, while Xero's launch material places multi-entity reporting, forecasting and stronger governance at the centre of the proposition. Ultra therefore deserves to be assessed as a different step in Xero's market direction, not simply as “Ultimate with another add-on”.
For UK businesses, there is an important timing point. Xero discussed Ultra at Xerocon London in 2026, but the plan is not yet shown as a standard UK pricing option as at the date of this update. We can learn from the Australian product and direction without pretending every Australian entitlement is already available in Britain.
Where is Xero Ultra available?
| Market / status | What we know as at 29 September 2026 |
|---|---|
| Australia | Live Xero Ultra launched on 7 July 2026. Xero announced Australian pricing at A$500 including GST per month. |
| UK | Announced / not on standard UK pricing page Xero showcased Ultra at Xerocon London as part of its direction for growing businesses. We would confirm current UK availability directly with Xero before building a migration decision around the plan. |
| Other markets | Availability and included features can vary by region. Do not assume the Australian plan is identical elsewhere. |
Australia therefore gives the market something more useful than a concept announcement: Ultra is already a real plan being used by businesses. Xero has published positive feedback from beta participant Trainwest, and the feedback we have heard around the wider Xero community has also been encouraging. We will keep this page updated as more real-world experience becomes available.
The 5 Xero Ultra features we would not overlook
1. Syft Advanced and multi-entity consolidated reporting
This is one of the most important changes for groups. Xero's September 2026 Ultra learning material covers connecting data, consolidating entities, reporting, benchmarking, custom KPIs, segments and ledgers, non-financial data, cash-flow forecasting, budgets, dashboards and AI-powered insights. For a group considering leaving an ERP, reporting capability is often one of the first questions: and this materially changes that conversation.
The detail matters. Xero's own September training includes chart-of-accounts layouts, user permissions, benchmarking, custom KPIs, segments and ledgers, non-financial data, budgets and dashboards. A group can therefore think beyond “can I produce a consolidated P&L?” and ask how management reporting, forecasts and operational measures should work across the entities.
2. Targeted data restore
Xero describes a high-priority service for restoring specific data errors without requiring a full-file rollback. That is a meaningful operational safeguard, although it should not be confused with migration validation. A newly migrated organisation still needs to be reconciled back to its source data and known differences need to be explained.
Xero Central now gives useful boundaries around this service. Ultra customers can request up to two targeted restore events in a financial year, and the priority service is aimed at errors from the previous six months. Examples include incorrect bulk imports and records affected by third-party app syncs. That makes the feature more concrete, but it is recovery support rather than a substitute for backups, controlled migration procedures or reconciliation.
3. Flexible permissions and segregation of duties
Growing finance teams need controls, not simply more users. Xero has highlighted flexible permissions as a way to strengthen governance and segregation of duties. This is particularly relevant where an ERP has historically been retained partly because of internal-control requirements.
4. Fast-track onboarding, migration and specialist support
Ultra includes front-of-queue access to Xero specialists and personalised onboarding and migration support in the Australian proposition. That does not replace specialist historical-data migration where the source is complex, but it strengthens the surrounding implementation experience.
5. The wider Xero platform: JAX, XeroForce and connected applications
The platform decision is bigger than Ultra alone. Xero is developing JAX, XeroForce, integrations with tools such as Microsoft 365 and Claude, and an ecosystem of more than 1,000 connected apps. A modern finance architecture does not always need every operational process inside one monolithic accounting product.
Xero Ultra: available now, rolling out and worth watching
| Capability | Status / context | Why it matters |
|---|---|---|
| Syft Advanced reporting | Core Ultra capability in Australia | Consolidation, forecasting, scenarios, KPIs and deeper group insight. |
| Targeted data restore | Core Ultra service in Australia | More focused recovery from specific data errors. |
| Fast-track specialist support | Core Ultra service in Australia | More support around onboarding and scaling. |
| Flexible permissions | Announced for Ultra; Xero said available shortly after Australian launch | Governance and segregation of duties. |
| JAX | Part of Xero's wider platform development | Automation, insights and increasingly agentic finance workflows. |
| XeroForce | Early access announced in 2026, with broader availability planned | No-code custom agents and connected workflows. |
Important: roadmap items move. We deliberately distinguish released features from announced features rather than presenting every Xerocon announcement as something every customer can use today.
Xero Ultra vs Xero Ultimate
Ultimate has historically been the top end of Xero's standard business plans in markets such as the UK. Ultra is aimed further up the complexity curve. The most important difference is not a checklist count; it is the combination of advanced financial intelligence, multi-entity reporting, stronger governance and higher-touch support aimed at scaling organisations.
| Question | Ultimate / established Xero plans | Ultra direction |
|---|---|---|
| Who is it aimed at? | Businesses needing Xero's broader established feature set. | Scaling and medium-sized businesses with greater finance complexity. |
| Multi-entity insight | Often supported through apps and reporting tools. | Syft Advanced and consolidated reporting are central to the proposition. |
| Governance | Xero user roles and existing controls. | Greater emphasis on flexible permissions and segregation of duties. |
| Support | Standard plan/support model. | Fast-track specialist access and personalised onboarding in Australia. |
What Xero Ultra does not automatically solve
Ultra strengthens several areas that matter to larger finance teams, but it does not turn every ERP requirement into a native Xero feature. This distinction is important when the migration starts from Sage 200, Business Central, Access, Intacct or another system that may be doing much more than bookkeeping.
| Requirement | What Ultra strengthens | What still needs a separate answer |
|---|---|---|
| Group finance | Consolidated reporting, forecasting and analytics through Syft Advanced. | How transactions are processed across entities, intercompany workflow and any specialist consolidation rules. |
| Data recovery | Targeted restore support for qualifying errors. | Migration validation, audit evidence, source backups and recovery for issues outside the service scope. |
| Governance | Greater emphasis on permissions and segregation of duties. | Approval chains, payment controls and very granular workflow requirements may still need apps or another platform. |
| Operations | A large connected-app ecosystem. | Manufacturing, MRP, warehouse, stock and industry-specific processes still need to be designed around suitable systems. |
| Scale | Xero explicitly positions Ultra for more transactions and complexity. | The actual transaction profile, API workload and live performance still need testing for demanding organisations. |
That is why we prefer to talk about a Xero-centred architecture rather than claiming Ultra is a universal ERP replacement. For some businesses the ledger can become simpler while specialist applications do the operational heavy lifting. For others, the integration and operational requirements mean an ERP remains the cleaner answer.
Is Xero still only for small businesses?
Calling Xero “small-business software” is increasingly incomplete. Xero itself still describes its platform around small businesses, but in 2026 it has also talked publicly about enterprise-style or enterprise-grade financial control, analytics and reporting. Ultra is explicitly designed for organisations whose complexity is increasing.
That does not mean company size has stopped mattering. It means requirements matter more than labels. A 100-person professional-services group may fit Xero extremely well. A much smaller organisation with complex manufacturing, warehouse, planning and operational requirements may not.
Can Xero Ultra replace an ERP?
Sometimes: but “replace an ERP” is the wrong first question. The better question is: which jobs is the ERP performing today, and where should each of those jobs live after the change?
| Requirement | Why Xero / Ultra may now be stronger | Where careful assessment is still needed |
|---|---|---|
| Group reporting | Syft Advanced brings consolidation and richer analytics closer to the Xero proposition. | Entity structure, eliminations and reporting design still need scoping. |
| Finance controls | Flexible permissions and connected approval apps strengthen governance. | Very granular role/workflow requirements may still favour specialist systems. |
| Forecasting and insight | Forecasting, scenarios, benchmarks, KPIs and AI insight are expanding. | Specialist FP&A requirements may still justify dedicated tools. |
| Operational workflows | Xero's app ecosystem lets specialist systems handle inventory, approvals and operations. | Complex manufacturing, MRP, warehouse or deeply customised ERP workflows may remain outside Xero. |
| Implementation | A Xero-centred architecture can be materially lighter than a traditional ERP programme. | Simpler software does not make data migration simple. |
Start by separating finance from operations
An ERP can accumulate jobs over many years. Some are genuinely operational and tightly integrated; others are there because the ERP happened to be the available system when a process was created. Before choosing Xero, we would list those jobs and decide which ones actually belong in the accounting ledger.
For example, a business may need sophisticated inventory planning but relatively straightforward statutory accounting. In that case, a specialist inventory platform integrated with Xero can be worth assessing. Another business may rely on deeply connected production, warehousing, costing and finance workflows where separating the ledger would add risk rather than remove complexity. Ultra does not make those two businesses equivalent.
Compare the future architecture, not the licence price
The meaningful comparison includes implementation, apps, integrations, reporting, support, training and internal administration. A Xero-centred stack can be lighter, but it is not automatically cheaper once every required component is included. Likewise, an ERP that looks expensive can still be good value if it is genuinely running critical operations well.
What about Xero's transaction and migration limitations?
This is where we think the conversation needs more nuance. Xero Ultra is explicitly being positioned for “more transactions” and more complexity. That is significant. But it would be irresponsible to translate that into “Xero has no limits now”.
In migration work, we separate three different issues that are often bundled together:
- Migration/API throughput: how quickly and reliably historical records can be created through available migration methods.
- Organisation performance: how a live Xero organisation behaves with the business's actual volume and transaction profile.
- Operational fit: whether Xero and connected applications can support the workflows the business needs after go-live.
Those questions need evidence and testing, not a generic internet number. We have migrated high-volume and multi-entity histories into Xero by restructuring, consolidating where appropriate and choosing the right migration design. Equally, we will say when a proposed structure is not sensible.
1. Migration throughput
Historical migration is a project workload. The source may contain years of invoices, bills, journals, bank transactions, contacts, allocations and attachments. APIs and import methods have practical behaviours that affect how this data is sequenced and loaded. A slower or more complex migration method is not, by itself, evidence that the live Xero organisation is unsuitable.
2. Live transaction profile
Total database size is a poor shortcut for this assessment. We want to know what the business creates each month: sales invoices, purchase bills, bank lines, journals, payments, credit notes and any transactions generated by connected apps. We also look for peaks. A business with seasonal batches can behave very differently from one with the same annual total spread evenly across the year.
3. Data design
Volume is only one dimension. An organisation with a huge Chart of Accounts, inconsistent contacts, excessive tracking combinations or years of legacy workarounds can be harder to operate than a larger but cleaner dataset. Migration is therefore an opportunity to redesign rather than reproduce every historic structure.
4. Integration load
Connected applications can create large numbers of records or API calls. The question is not simply whether Xero has an app for a job. We need to understand what the app sends, how often it sends it, what happens when a sync fails and whether the resulting accounting records remain usable for finance.
5. Reporting and operational fit
A platform can perform well technically and still be the wrong system. If the business needs complex manufacturing, warehouse or planning workflows that cannot be supported cleanly by Xero and suitable connected applications, the correct conclusion may still be to retain or replace the ERP with another ERP.
What Xero Ultra changes for ERP-to-Xero migrations
For Migrate My Accounts, this is the most interesting part. We already migrate organisations from Sage 200, Access Dimensions and Financials, Microsoft Dynamics NAV and Business Central, Sage Intacct, Exchequer and other complex environments into Xero. Ultra strengthens the destination-side story for organisations that previously worried they would immediately outgrow Xero.
The migration itself still needs accounting judgement. ERP dimensions may need to become Xero Tracking or be redesigned. Historical allocations, foreign currency, VAT, contacts and document references need to remain meaningful. Operational functions may move to specialist apps. The final Xero organisation needs to reconcile to the agreed source position.
What changes by source system?
| Source environment | Typical migration question | What needs particular care |
|---|---|---|
| Sage 200 | How much transaction history and nominal detail should remain live? | Nominal structure, allocations, VAT, departments/cost centres and high-volume histories. |
| Access Dimensions / Financials | How should periods, dimensions and legacy references map into Xero? | Period-versus-date logic, document references, VAT and source extraction. |
| Business Central / NAV | Which finance history moves and which operational processes stay in specialist systems? | Dimensions, customer/vendor entries, currencies, allocations and integration boundaries. |
| Sage Intacct | How should a more dimensional cloud-finance structure be simplified? | Dimensions, entities, reporting requirements, currencies and historical comparatives. |
| Exchequer | How do we preserve useful transaction and document history from a legacy environment? | References, tax, allocations, reporting structures and extraction quality. |
The source-system name is only the starting point. Two Sage 200 databases can require completely different migration designs because one is a straightforward finance ledger while the other contains years of high-volume transactional history and complex departmental coding.
That is why we do not treat ERP-to-Xero work as a CSV conversion exercise. See our ERP to Xero migration approach or see how we validate a completed Xero migration.
What should you assess before moving a complex business to Xero?
- Transaction volume by type and by month: not simply total database size.
- Number of entities and whether consolidated reporting is required.
- Chart of Accounts, departments, cost centres, dimensions and projects.
- Foreign currency and historical revaluations.
- VAT/GST/tax treatment and historical reporting requirements.
- Customer and supplier allocations and aged-ledger expectations.
- Inventory, manufacturing, purchasing and operational workflows.
- Approval and segregation-of-duties requirements.
- Connected applications and integration design.
- How much historical detail genuinely needs to be live in Xero.
- How the final migration will be reconciled and evidenced.
We would assess the move in four stages
- Fit: confirm that Xero and the proposed app stack can support the future finance and operational requirements.
- Data: profile the source history, volumes, currencies, dimensions, allocations and known data-quality issues.
- Design: agree what moves in detail, what is consolidated, how codes map and which systems own each process after go-live.
- Proof: migrate into a controlled environment, reconcile the result and resolve differences before treating the destination as complete.
Ultra can improve the destination proposition, particularly around reporting, support and recovery. It does not remove any of those four stages. In our view, a stronger destination makes disciplined migration more important because businesses are more likely to depend on Xero for a wider range of finance decisions after go-live.
Our perspective after complex Xero migrations
We like Xero, but our job in a migration is not to force every business into it. The useful change in 2026 is that businesses have more reason to assess Xero on its current capabilities rather than on an old perception of what Xero was built for.
Ultra, Syft, stronger analytics, a growing automation layer and the wider app ecosystem all push that boundary. For some organisations, that can create a credible third path between staying on an ageing legacy system and implementing another large ERP.
For others, an ERP will remain the right answer. The differentiator is knowing enough about the source system, the accounting data and Xero to tell the difference.
That is also why we are interested in what happens in Australia. Ultra is no longer just a launch slide there; it is an actual plan with published entitlements, support documentation and training. The early direction is encouraging, especially for multi-entity reporting and businesses that want more control without a traditional ERP implementation. We still want to see how the proposition develops across markets and how it behaves across a wider range of real organisations.
For a UK business considering an ERP exit today, we would therefore separate two decisions. First, is Xero itself, with the right connected applications, a suitable destination? Second, does the business case depend specifically on an Ultra feature that is not yet generally available in the UK? Keeping those questions separate avoids building a migration plan around an announcement rather than an available capability.
Xero Ultra FAQs
Is Xero Ultra available in the UK?
Xero showcased Ultra at Xerocon London in July 2026, but as at 29 September 2026 it is not shown as a standard plan on Xero's UK pricing page. Check current availability with Xero before making a purchasing or migration decision.
Is Xero Ultra already live anywhere?
Yes. Xero Ultra launched in Australia on 7 July 2026.
Does Xero Ultra remove all Xero transaction limits?
We would not make that claim. Xero is explicitly positioning Ultra for more transactions and greater complexity, but migration throughput, live performance and operational fit should still be assessed against the actual workload.
Does Ultra mean Xero is now an ERP?
Not necessarily. Xero describes Ultra as providing ERP-grade or enterprise-style capabilities in areas such as control and reporting. Whether it replaces an ERP depends on what the existing ERP actually does for the business.
Can we migrate full ERP history into Xero Ultra?
The answer depends on the source system, history, volume and required structure. We routinely scope detailed historical migrations rather than assuming opening balances are the only option.
What does targeted data restore actually cover?
Xero says the priority service can help with qualifying large data errors such as incorrect bulk imports or records affected by third-party app syncs. It is limited in scope and timing, so it should be treated as a useful recovery service rather than a replacement for migration controls and reconciliation.
Is Syft Advanced only useful for consolidated accounts?
No. Xero's Ultra training also covers benchmarking, custom KPIs, segments, ledgers, non-financial data, budgets, forecasts, dashboards and AI-powered insights. Consolidation is a major use case, but it is not the whole reporting proposition.
Should we wait for Ultra before migrating to Xero in the UK?
Not automatically. If the business case works with capabilities already available in the UK, the migration decision does not necessarily need to depend on Ultra. If a specific Ultra-only capability is essential, confirm its UK availability and terms with Xero before committing to the project.

