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.
Data migration
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
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.
AI drafts field-by-field mappings and transformation rules and flags likely duplicates and inconsistent values. Our consultants confirm every rule with your team.
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.
We run full trial migrations into test environments, including restart and volume tests, and reconcile counts and checksums against the source after every run.
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.
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
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.
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.
Nothing gets lost in translation. Original identifiers, versions and parent-child relationships are kept, and every total is reconciled against your source counts.
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.
Documents, not just data. Records, attachments, versions, metadata and folder structures come across, with security and retention rules applied.
Why migrations slip
Your current system knows things nobody wrote down. Business rules live in custom code, database triggers, spreadsheets and people's heads.
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.
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.
Cutover gets treated as a weekend, not a plan. Without rehearsals and a way back, go-live becomes a gamble.
AI-augmented migration
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.
Track record
Different clients and different systems, with the same care for the records their teams depend on.
AWH
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 storyNSW Spatial Services
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 storySkyMesh
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 storyState Library of NSW
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 storyYouth not-for-profit
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
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
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.
Migration work
We carried out the migration of AWH's operational data from its AS400 platform, a mainframe-class system, into its new platform: mapped, cleansed, rehearsed and cut over with every record accounted for. After the original prime contractor left, AWH kept us on through retained services.
AWHNSW Spatial Services replaced the two systems behind the naming of the state's roads and places. We built the new web portal, connected it to Jira as the workflow engine that runs every naming proposal, and brought both name registers across from the previous databases.
NSW Spatial ServicesSkyMesh moved its full customer-care history from its ticketing tool across to Dynamics 365, then gave its team a guided way to win customers back.
SkyMeshA connected Dynamics 365 platform for enquiries, events, venue hire, memberships and giving, delivered launch by launch since November 2024.
State Library of New South WalesCommon questions
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.
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.
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.
We agree up front what moves: open records, history, attachments and documents. Anything left behind is a deliberate decision, recorded and signed off.
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.
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.
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
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.