Import data from your current system
How data migration works during a Traiq rollout — what we move, what you export, and how we check it landed correctly before go-live.
- Audience
- Implementation, Admin
- Stage
- Configure
- 5 min read
- Updated
Most of a rollout’s risk sits in the data. Here’s how migration works, who does what, and how you confirm the numbers are right before anyone goes live.
How it works
- 1
Agree what moves
Not everything needs to come across. We agree the master data — people, items, locations — and how much history you actually need.
- 2
You provide exports
You export from your current system, or give us access to do it. We map those files to Traiq.
Cleaner source data means a cleaner import. It’s worth fixing obvious errors at the source first.
- 3
We load and you review
We import into an environment you can check. You spot-check records you know well before it’s signed off.
- 4
Final load at cutover
Just before go-live we do a final, up-to-date import so nothing is stale on day one.
Check it landed
| What to check | How |
|---|---|
| Counts | Record counts in Traiq match your source exports. |
| Opening balances | Stock, ledgers or registers reconcile to your source on the cutover date. |
| Spot checks | A handful of records you know by heart look exactly right. |