Switch clean. Start your next job in Assaya.
Whatever you are on now, you do not need a migration project to leave it. Start your very next job in Assaya: no downtime, nothing to re-survey. Your old system keeps your closed jobs, and your live history comes across only if and when you want it.
Want your history too? It comes across clean.
You never have to bring your back-catalogue to switch — but when a firm wants to, it carries faithfully. We rebuilt one national government job from nothing more than its standard exported reports, as a staged proving run on an Assaya instance. Every pin landed where it belonged.
138 pins in exact position
Each seal dropped onto the drawing at the coordinates it already held — not re-plotted by hand, carried across from the source reports.
163 photos reattached
Before, during and after images matched back to the right seal, so the evidence trail arrived intact rather than in a loose folder.
Staged in under a day
From files in to a checked, ready instance out — fast enough that a crew could keep recording in its old system while the rebuild staged in the background.
If you want your history brought across
Optional — you can simply start clean instead. But if you'd like your live jobs to come with you, the route is proven and plain. You keep working throughout, and you check the staged instance before anything switches.
Export from your current tool
Pull the standard PDF reports your system already produces, plus an optional CSV. Nothing bespoke — the same documents you would send a client.
Send us the files
Hand the exports over, or run our customer extractor yourself — it runs in your own browser, on your own session, so the data never leaves your hands.
We stage your jobs
We rebuild each job on your own isolated Assaya instance: pins to their exact drawing positions, photos onto the right seals, statuses mapped across.
You check it, the crew carries on
You review the staged instance against the old one and sign it off. The crew stays in the old system until you are satisfied — then you switch.
Leaving must always be as easy as joining
The whole point of moving to Assaya is that your records are portable. So we built the migration two ways: hand us your exports, or run the customer extractor yourself — it works entirely in your browser on your own login, which keeps the transfer inside your GDPR data-portability rights and means nothing passes through a third party.
That same principle applies to Assaya itself. You can export your full data at any time, and if you ever leave you get a handover pack on the way out. Your record is never held hostage — not by the system you are leaving, and not by us.
- Customer-run extractor — runs in your browser, on your session, so your data stays end to end yours.
- Full data export from Assaya on demand, plus a handover pack if you ever move on.
- Your own isolated instance and database, UK-hosted in London.
Straight answers
Do the pins really land in the right position?
Yes. The pin positions come straight from your existing reports, so each seal drops onto the drawing at the exact coordinates it already held. On the national government job we rebuilt as a proving run, all 138 pins landed in position. Nobody re-plots anything by hand.
What do you need from us?
The standard PDF reports your current system exports, and optionally a CSV. That is usually enough to rebuild jobs, pins, photos and statuses. If you would rather not hand files over, you run the customer extractor yourself — it works in your own browser on your own session.
How much downtime is there?
None. Your crew keeps recording in the old system while we stage the rebuild in the background. You only switch once you have checked the new instance and signed it off, so there is no window where nobody can log a seal.
Do I have to migrate my old jobs — and what does it cost?
No. The simplest switch is to start clean from your next job, with nothing to bring across. If you do want your history, you can run the customer extractor yourself in your browser at no cost — or we'll scope a done-for-you migration with you (quoted per job and agreed in writing before any work begins). Either way you see the staged instance before you commit.