Leaving legacy data behind? Plan the archive before you migrate

By DataForge team16 November 20265 min read

A 12 November study of 1,115 IT transformations found 66% skip full data migration. Here's how NZ firms should handle the data they leave behind.

What the study found

On 12 November, the German data migration firm Natuvion and NTT DATA Business Solutions released their Transformation Study 2026. The survey asked 1,115 executives and IT professionals across 15 countries about the most recent IT transformation they'd worked on. According to the Natuvion release, 66% of the companies surveyed didn't move all of their existing data and processes into the new system. They either started fresh or migrated selectively.

The systems being replaced are old. The release says 38.4% of them were more than ten years old and nearly 10% were over 16. Delivery was rough for most respondents: more than 80% went over their transformation budget and 79.5% fell behind schedule. The study's landing page adds that 71% had to change their migration strategy partway through the project, and 26% named poor data quality as their biggest challenge.

One trend matters for compliance teams. Meeting regulatory requirements was the second most common unexpected challenge, cited by 25.9% of respondents. In the previous year's study it ranked eighth, according to the release.

Why the leftover data is the expensive part

Selective migration makes sense on paper. Moving fifteen years of half-clean customer, supplier and transaction records into a new ERP or CRM slows the project down and carries the old system's data problems into the new one. Most project teams cut the scope to a couple of years of open items and active master data, and treat everything older as history.

The trouble starts when nobody decides where that history will live. Old invoices, payroll and job records still get pulled for audits, warranty claims, disputes and the occasional Official Information Act or Privacy Act request. The cheapest-looking option is to keep the old server running in read-only mode "for now". Two years on, the business is still paying for hosting, database licences and support on a system that no longer gets security patches, and the one staff member who knew how to run its reports has left.

Public sector audits show the same pattern. In June, South Australia's Auditor-General reported that agencies kept legacy systems running because they lacked the funding, resourcing or a clear path to replace them. Some of those agencies also had incomplete asset inventories and only limited formal risk assessments. Private firms in New Zealand rarely get audited on legacy systems at all, so the same drift goes unnoticed for longer.

The study does point to savings. Natuvion reports that 48.1% of companies saved on IT infrastructure and 35% saved by reducing data volumes. Those savings only appear once the old platform is switched off, so a plan that leaves it running indefinitely forfeits them.

What NZ rules mean for the data you leave behind

New Zealand law pulls retention in two directions. Inland Revenue says businesses must keep records of all cash and electronic sales and purchases for 7 years, and it accepts electronic records. Any archive of an old finance system has to remain usable for that full period, whether or not the source application still exists.

Location matters too. Storing business records outside New Zealand generally needs the Commissioner's approval under section 22(2BA) of the Tax Administration Act 1994. Firms that use a provider on Inland Revenue's approved list don't need that approval, but they remain responsible for their tax obligations. A cheap overseas archive bucket bought during a migration can quietly breach that rule.

Privacy law pushes the other way. Information Privacy Principle 9 says an agency holding personal information must not keep it for longer than is required for its lawful purposes. Old CRM contacts, former staff files and marketing lists rarely carry a seven-year obligation, so keeping all of them "just in case" adds privacy risk with nothing gained. A sound archive plan keeps transaction records for their legal period and deletes personal data on a separate, shorter schedule.

Reading the numbers with care

Natuvion and NTT DATA both sell migration and decommissioning services, and the release promotes Natuvion's own archiving product. The sample also leans large. The release says 42% of participating companies employ between 1,000 and 4,999 people and 37% earn more than €1 billion a year. Of the 15 countries surveyed, only Germany, Austria, Switzerland and the United States are named, so there's no published Australian or New Zealand breakdown. The vendors haven't published how far projects ran over budget, only the share that did.

Even so, the direction lines up with what mid-sized NZ firms tell us about replacing old accounting packages, job management tools and homegrown databases. Teams plan the cutover in detail and leave the old data to sort itself out afterwards. The scale is smaller here, but the retention obligations are the same.

Practical next steps

If you're planning an ERP, CRM or line-of-business replacement in 2027, we'd make the decommissioning plan part of the business case from day one. As part of a wider digital transformation programme, that means:

  • Listing every data set in the old system and recording its retention basis (tax, employment, contract, customs or none) along with a named owner.
  • Deciding what migrates in full, what migrates as summaries and what goes to an archive, before you choose the migration tooling.
  • Choosing an archive format that's readable without the original application, such as structured exports with a documented data model, and testing a real audit-style query against it before go-live.
  • Confirming that any offshore archive is on Inland Revenue's approved provider list or covered by Commissioner approval.
  • Setting deletion dates for personal data that has no legal hold, so the archive doesn't become a permanent copy of every former customer.
  • Putting a switch-off date and budget line for the old platform into the project plan, with someone accountable for hitting it.
  • Holding contingency for data quality fixes, since poor data was the most common major challenge in the study and mid-project strategy changes were the norm.

For firms already running an old server "temporarily" after a past migration, an hour spent listing what's on it, who still uses it and what it costs each year is usually enough to show whether a proper archive pays for itself. Our ERP team sees that question come up most often around finance and payroll history.

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