insight

WorkflowMax in 2026: what actually happened, and what your firm should do about it

Xero retired the original WorkflowMax and BlueRock relaunched it as a new product with a new API - which quietly broke the integrations thousands of NZ firms relied on. A plain guide to your real options: settle into the new WorkflowMax, move to XPM or Karbon, or use the moment to fix the workflow properly.

If your firm ran the old WorkflowMax, the last couple of years have been genuinely confusing. Here is the story in plain terms, and a straight look at the options.

What actually happened

Xero retired the original WorkflowMax product it had owned for years. The brand was bought by BlueRock, an Australian advisory group, and relaunched as WorkflowMax by BlueRock - a rebuilt product, not a re-skin of the old one.

The practical consequences most firms discovered the hard way:

  1. It is a different product. Screens, workflows and features moved. Some things got better, some things a firm relied on changed or disappeared. "We already know WorkflowMax" was only partly true.
  2. It is a different API. The old WorkflowMax API is gone; the new product has a new v2 API (modern JSON REST with OAuth2 - technically nicer, but not compatible). Anything wired to the old one - Xero sync quirks someone had tuned, reporting feeds, Zapier hooks, that custom export a contractor built in 2019 - broke at migration or was simply never rebuilt.
  3. The data had to move. Migration tooling existed, but "the data arrived" and "the practice works like it used to" are different finish lines. Plenty of firms are still somewhere between the two.

None of this makes the new WorkflowMax a bad product. It makes it a decision point that thousands of NZ firms were pushed through, whether they wanted one or not.

The three real options

Option 1 - Settle into WorkflowMax by BlueRock properly

If the new product fits how you quote, track and bill jobs, the right move is often to finish the migration you technically already did: audit what was connected to the old system, rebuild those connections on the v2 API, and fix the workflow gaps you have been working around by hand. The new API is good; the integrations just have to be rebuilt, not assumed.

Choose this when: the product fits, your team knows it, and the pain is mostly the broken plumbing around it.

Option 2 - Move to Xero Practice Manager or Karbon

If you were only on WorkflowMax because it was Xero's, XPM is the natural home - same family as your ledger, and the tool most NZ accounting practices standardise on. If your pain is workflow, email and team coordination more than job costing, Karbon is the strongest practice-management platform on the openness front (modern API, real webhooks) and plays well with automation.

Choose this when: the disruption already happened anyway - if you have to re-learn and re-integrate regardless, it is the cheapest moment you will ever get to choose the right platform instead of the familiar one.

Option 3 - Use the moment to fix the workflow itself

The quiet opportunity. Most firms did not love their old WorkflowMax setup; they loved that it was set up. Before rebuilding everything exactly as it was, it is worth asking what the workflow should be: what gets automated (client onboarding, AML evidence, re-keying into the ledger), what gets retired, and only then which tool carries it.

Choose this when: the honest answer to "was the old setup good?" is no.

What a proper migration assessment covers

Whichever option, the work is the same shape - and it is bounded, not open-ended:

  • Inventory what was actually connected. Old integrations, exports, Zapier hooks, the spreadsheet someone refreshes weekly. Most firms find at least one connection nobody remembered until it stopped.
  • Map the data. Clients, jobs, time, WIP, templates - what moves, what gets archived, what was junk anyway.
  • Rebuild the plumbing on the new platform's API - or the new tool's - rather than re-keying around the gap forever.
  • Test against real jobs, not a demo file, before the team switches.
  • Leave it documented, so the next change is not archaeology.

For a small practice this is days of focused work, not a quarter-long project. The expensive version is the alternative: a year of staff quietly hand-carrying data across a gap that used to be automated.

Where we fit

We do this work for NZ accounting firms: the assessment, the honest recommendation between the three options above (we are independent - we do not resell any of these platforms, so we genuinely do not mind which one you land on), and the build - migration, rebuilt integrations, and the automation the moment makes possible.

If your firm is somewhere in the WorkflowMax limbo - migrated but not really settled, or still deciding - tell us where you are up to. We will tell you straight which option fits and what it involves.

want this sorted

Tell us what is hurting.

A no-obligation chat, then a straight answer. Most owner-operator IT problems are smaller than they look once a real person digs in.