Data migration

The hard part of any new system is the data.

We move your data out of the systems you're leaving and into Microsoft Dynamics 365, Business Central and Dataverse. AI does the heavy lifting on analysis and mapping. Our people check every rule, rehearse every run and account for every record before you switch over.

Our method

Six steps, rehearsed until they're boring.

01

Look first

We take exports, schemas or database access and run our AI tools over them to see what's really there: tables, fields, relationships, volumes, duplicates and gaps. We won't commit to an estimate until we've done this.

02

Map with AI, confirm with people

AI drafts field-by-field mappings and transformation rules and flags likely duplicates and inconsistent values. Our consultants confirm every rule with your team.

03

Build repeatable runs

Migration scripts are version-controlled and can be run again and again. Original identifiers and parent-child relationships are kept, so every migrated record traces back to where it came from.

04

Rehearse until the numbers match

We run full trial migrations into test environments, including restart and volume tests, and reconcile counts and checksums against the source after every run.

05

Cut over in planned waves

We agree a quiet period, migrate production in waves, pick up anything created or changed since the last wave, and keep a tested way back to your current system until you've signed off.

06

Account for everything

Every in-scope record ends up migrated, deliberately excluded or logged as an approved exception. We recommend switching your previous system off only after you've accepted the result.

Why Experience Digital

Why migrations go well with us.

01

We don't need an API. We extract directly from the database or a full export, with read-only access, which is how we've moved data off AS400, Oracle, Informix and records management systems.

02

We prove it on your real data first. An early rehearsal with your own data confirms completeness, mapping, document and version handling, restart and throughput before we migrate at scale.

03

Nothing gets lost in translation. Original identifiers, versions and parent-child relationships are kept, and every total is reconciled against your source counts.

04

Run old and new side by side where it matters. For operational systems we can phase the move, with clear rules on which system is the source of truth and a rehearsed way back.

05

Documents, not just data. Records, attachments, versions, metadata and folder structures come across, with security and retention rules applied.

Why migrations slip

Most of the risk sits in the data you bring with you.

01

Your current system knows things nobody wrote down. Business rules live in custom code, database triggers, spreadsheets and people's heads.

02

The data is messier than anyone expects. Duplicates, free-text fields, inconsistent values and orphaned records turn up late, when they are most expensive to fix.

03

Estimates get made before anyone looks. A proof of concept is never the reality for a migration, so we look at the real data first.

04

Cutover gets treated as a weekend, not a plan. Without rehearsals and a way back, go-live becomes a gamble.

AI-augmented migration

AI does the heavy lifting. People make the calls.

AI shortens the slowest parts of a migration: working out what's in your current system, mapping it and finding the problems. Nothing it suggests touches production data until our people have validated it.

What AI does

  • Profiles source data and schemas, including systems with no usable API
  • Suggests field mappings and transformation rules
  • Finds duplicates, gaps and inconsistent values early
  • Generates and documents the migration scripts
  • Drafts reconciliation reports and exception lists

What our people do

  • Agree with you what moves, what stays and what gets archived
  • Approve every mapping and transformation rule
  • Handle sensitive data under your governance
  • Run the rehearsals and sign off the reconciliation
  • Own the cutover plan and the way back

Track record

The organisations. The data. The work.

Different clients and different systems, with the same care for the records their teams depend on.

AWH

Operational data, one module at a time

AS400 / DB2 → custom cloud platform

We brought AWH's operational data across from DB2 and kept it in sync with its new cloud platform. The migration engine and DB2 driver we built let the business move across one module at a time while both systems ran alongside each other.

Read their story

NSW Spatial Services

The state's road and place-name registers

Oracle / Informix → PostgreSQL

About 596,000 rows brought across for both of NSW's road and place-name registers, with re-runnable scripts and no business interruption.

Read their story

SkyMesh

Customer history and billing, brought together

Request Tracker / TINA → Dynamics 365 / Business Central

Full customer-care history brought across from Request Tracker, alongside subscriptions, accounts and billing from TINA. The billing migration was validated table by table a year later.

Read their story

State Library of NSW

Enquiries and their full history

RefTracker → Dynamics 365

Cases, contacts, emails and attachments brought across from RefTracker so the Library's team can work from one connected enquiry history.

Read their story

Youth not-for-profit

Case records with a tighter security model

Client, participation and case-note records

Records exported, cleaned and re-imported into a new security model through a rehearsed cutover, with the client kept anonymous.

Health provider

Patient records matched and checked

Best Practice matching → Dynamics 365

Patient records matched using Microsoft Copilot's Analyst agent inside the provider's own Microsoft 365 environment. People reviewed every exception before records were loaded into Dynamics 365 with no errors.

Privacy first

Health, child and financial data, handled properly.

We have migrated and managed health records, information about children and families in not-for-profit programs, and government datasets. We apply the same privacy rules on every migration, keep data in environments you approve, and agree up front which tools can touch it.

Common questions

Questions about data migration.

Can you migrate documents and records management systems?

Yes. We migrate documents, versions, metadata, hierarchies and security from records management systems, and account for every item as migrated, excluded, kept in an archive you can still access, or logged as an approved exception.

How long will our migration take?

It depends on the data, which is why we look first. After a short assessment we'll give you a plan with rehearsal and cutover dates, and tell you honestly what's clean, what isn't and what it will take.

Can we keep working during the migration?

Yes. We plan a quiet period and cut over in waves, picking up anything that changed since the last run, so the business keeps moving.

Will our history and documents come across?

We agree up front what moves: open records, history, attachments and documents. Anything left behind is a deliberate decision, recorded and signed off.

Is it safe to use AI on our data?

We agree with you which tools touch your data and where they run. Your data stays in your tenant or in environments you approve, and AI suggestions are never applied to production records without validation.

What if our current system has no export or API?

Our method doesn't depend on the current system's APIs. If we can get to the database or a full export, we can usually work with it, and that includes mainframe and AS400 systems.

Do you only migrate into Dynamics 365?

Most of our migrations land in Dynamics 365, Business Central or Dataverse. We have also moved data into PostgreSQL and cloud data platforms on Azure and AWS when that was the right home for it.

NSW Government ICT Services Scheme Advanced Supplier, approved for business analysis, software support and maintenance, custom application development, CRM and case management, and information management.

Next step

Tell us what data you need to bring across.

Send us a rough picture of your current system and the data in it. We'll tell you straight how we'd approach it and what we'd need to see first.

Book a migration readiness assessment