Gisborne's 18-month ERP rollout hits 57 months: lessons for NZ

By DataForge team23 November 20264 min read

Gisborne District Council's TechnologyOne programme has run 57 months and cost $8.1m, with seven workstreams still open. Here's what NZ firms can learn.

What happened at Gisborne

Gisborne District Council announced its move to TechnologyOne's cloud ERP in May 2022. The plan was a staged upgrade over 18 months, starting with finance and budgeting, procurement, and HR and payroll, according to TechnologyOne's media release. On 19 November 2026, IT Brief reported through Local Democracy Reporting that the programme has now run 57 months from the start of procurement. It has cost $8.1m against a 2022 to 2026 budget of $9m, and seven workstreams are still outstanding. The five finished workstreams include finance, procurement and supply chain, and contract management. The seven unfinished ones include property and rating, regulatory and compliance, and the customer portals and online services that ratepayers use directly.

The council's LGOIMA response, as IT Brief reported it, says the delay came from system configuration, data migration and business process work taking more time and resources than expected. A TechnologyOne spokesperson told IT Brief the programme has taken longer "as requirements and priorities have been refined with the council." The council has approved $3.5m for 2026/27. Funding after that depends on the 2027 to 2037 Long Term Plan, which the council expects to adopt in June 2027.

Why the numbers drifted

The first estimate, in the 2021 to 2031 Long Term Plan, was $4.5m across two financial years. The council told IT Brief that this amount was set aside before detailed scoping and that the $9m budget came from later estimates. Many organisations repeat the same pattern. A figure produced early to win a place in a funding round becomes the figure people remember, even though nobody had mapped the processes or counted the data when it was written.

Data migration is the part of the Gisborne programme that keeps growing. In March 2024 the council went to market for a partner to move 2.5 million records from its Objective content management system into TechnologyOne. In October 2026 it advertised a fixed-term, two-year data and business analyst role to support the migration of legacy systems, according to IT Brief. The council's migration work is therefore staffed to run until about late 2028.

Gisborne isn't the only council to have trouble with the same platform. RNZ reported in September 2023 that Rotorua Lakes Council's OneCouncil rollout cost about $18.4m, against $3.456m first allocated in 2016. Rotorua's second phase went live about five years later than planned. Rotorua was the first NZ council to implement the property and rating module, which pushed up configuration costs, and its time-and-materials contract had assumed a timeline of 19 to 21 months.

The hard modules come last

The order of work at Gisborne deserves attention. In finance, procurement and contract management, vendor templates fit most organisations with modest changes. Property and rating, regulatory work and public portals involve local rules, decades of historical records and integrations with other council systems, so they need far more configuration and testing. Five of twelve workstreams finished after nearly five years overstates the progress made, because the remaining seven are the heaviest. Rotorua's experience as the first council on the property and rating module points the same way.

Private businesses hit the same wall. A distributor or manufacturer replacing its ERP can often get the general ledger and purchasing live fairly quickly, then stall on job costing, warehouse logic, customer pricing rules or a customer portal, which is where its own way of working sits. While the business waits, the old system keeps running, licence and support fees are paid on both platforms, and staff enter the same data twice.

What it means for NZ businesses

Gisborne's spending to date is still within the approved budget, so a quick reading of the figures can miss the real cost, which is time. A programme running more than three times its planned length keeps legacy systems alive for years, takes internal staff away from their normal work and delays the benefits the business case promised. The council's stated aims were stronger business continuity, fewer manual processes and better information management, and most of those benefits depend on the unfinished workstreams.

When we scope an ERP replacement, any budget set before process mapping and a data inventory is a placeholder. The Gisborne figures show why that label matters: the $4.5m estimate turned into a $9m budget, plus $3.5m more for the current year, and funding beyond 2026/27 hasn't been approved. The council hasn't published a total cost or a completion date.

Contract structure also decides who carries the overrun. Rotorua's contract was time-and-materials, so the extra hours landed on the council. Gisborne's contract terms haven't been published. Fixed-price stages move some risk to the vendor, but they only hold up when the scope behind each stage is firm, so the case for detailed discovery comes back again. Our digital transformation guidance treats the migration and parallel-running plan as part of the business case from day one.

Practical next steps

  • Label any ERP or core-system budget set before discovery as an estimate in board papers, and commit to a re-baseline once process mapping is finished.
  • Count records, document types and data quality issues in every legacy system before you sign. Gisborne's 2.5 million records needed a separate tender and later a dedicated two-year role.
  • Ask your vendor or implementation partner to report estimated effort remaining for each workstream alongside the count of modules complete, so the heavy modules are visible.
  • Schedule at least one complex, business-specific module in the first stage so the hard configuration questions come up in year one.
  • Cost the period of running legacy and new systems side by side, and set a target switch-off date for each old system.
  • Read your contract type closely. Time-and-materials terms leave overruns with you, and fixed-price stages need tightly defined scope to mean anything.
  • Name an internal owner for data migration and agree backfill for seconded staff before kickoff, because configuration and migration work draws on the same people who run the business.

Want to know what this means for your organisation? Our team in Auckland can show you your top three opportunities in a free 30 minute assessment.

Get my free assessment How we help
Get new articles by RSS