Services · Migrate
Every record moved. Threading intact.
Move everything. Break nothing. We built our own connectors rather than reselling somebody else’s - which is why we can quote a fixed price, run a dry run first, and deploy the whole engine inside your cloud if your security team asks.
What carries across
The records the engine moves.
This is the commodity half - it should be automated, and it is. What matters is fidelity at the edges: threading, authorship, timestamps, attachments.
Tickets & conversations
Full thread, in order, with public replies and internal notes kept on the right side of the line.
Contacts, users & companies
Deduplicated on email or external ID, with the company relationship preserved.
Custom fields
Mapped one by one to the destination’s field model. Anything without an equivalent gets a decision, not a silent drop.
Tags & labels
Carried across as-is, or consolidated if you want the move to double as a clean-up.
Attachments & inline images
Re-uploaded and re-linked to the right message - the step most exports get wrong at volume.
Knowledge base articles
Content, structure, authorship and published state, with redirects from the old URLs.
Agents & teams
Recreated so historical assignment still points at a real person.
Timestamps & authorship
Original created and updated times, and the real author on every message - not the API user.
The other half
The configuration somebody has to rebuild.
No exporter produces these. If your migration vendor stops at records, this list is what lands on your team the week you go live - so we rebuild it for you on Intercom, Freshdesk and Pylon.
Triggers & automations
Rewritten in the destination’s own model - the logic rarely maps one-to-one.
Macros & saved replies
Including the placeholders, which use different syntax on every platform.
SLAs & business hours
Policies, targets, escalation paths and holiday calendars.
Views, queues & routing
How work reaches the right person on Monday morning.
Bots & AI agents
Fin, resolution bots, answer content and the hand-off rules.
Channels & integrations
Email domains, forwarding, Slack, CRM and issue-tracker links.
The platform
The engine behind every project.
We do not resell a migration tool. We built one, we run your project on it, and where your security team requires it we deploy it inside your own cloud account.
Purpose-built connectors
Written and maintained by us against each platform API, rather than resold. Rate-limit aware, resumable, and updated when a vendor changes their API.
Field-level mapping
Every object and field mapped explicitly, with transformations where the models disagree. The mapping is a document you approve, not a hidden default.
Dry runs into a sandbox
The whole migration, rehearsed into a trial workspace. You open the records that matter and sign off before the live run is scheduled.
Reconciliation reporting
Record counts compared source to destination, with every discrepancy itemised and explained rather than averaged away.
Delta sync at cut-over
Anything created during the bulk run is caught up on cut-over day, so there is no gap and no downtime.
Runs in your cloud
Deployable into your own AWS or Azure account, so customer data never leaves your infrastructure. This is what usually unblocks security review.
Already working with us?
Log in to your project.
Track a running migration, review a dry run and pull the reconciliation report for your project.
How it runs
Understand. Map. Move. Validate.
You approve the outcome of each stage before the next one starts.
Understand
We map the data, relationships and requirements that matter - including the ones nobody documented.
Object counts, custom fields, attachment volume, integrations touching the desk.
Map
We align your existing data with the structure of the destination - and tell you exactly what carries across before anything moves.
A written mapping document you sign off. No surprises after go-live.
Move
A dry run into a sandbox first, then the live run on a schedule your team agrees to.
Delta sync catches everything created while the migration ran.
Validate
We check the outcome against record counts on both sides so you can move forward with confidence.
Reconciliation report per object, plus a spot-check list you run yourself.
Validation
Don’t trust the migration. Check it.
Every run ends with a reconciliation report: record counts per object on both sides, a list of anything skipped and why, and the mapping decisions applied. You get the numbers, not an assurance.
- Counts per object, source vs destination
- A skipped-records list with the reason for each
- Spot-check links into both platforms for the same record
- Delta sync report for everything created mid-migration
object source dest delta
conversations 41,208 41,208 0
messages 386,441 386,441 0
contacts 18,904 18,904 0
companies 2,113 2,113 0
attachments 27,556 27,553 -3
articles 412 412 0
skipped (3)
attachment 90311 source 404 - file
deleted before migration
attachment 90884 source 404 - file
deleted before migration
attachment 91002 0 bytes at sourceSecurity
Your data can stay in your cloud.
The standard engagement runs on our infrastructure with credentials scoped to the minimum the APIs allow, and access revoked at hand-over. When that is not acceptable - regulated industries, data-residency rules, an enterprise security review - we deploy the engine inside your own AWS or Azure account instead.
Self-host / white-label
The engine runs in your account. Customer data never touches ours.
Least-privilege credentials
Scoped API tokens - and we tell you exactly which scopes and why.
Revoked at hand-over
Access ends when the project does. You get written confirmation.
Data residency
Run the migration in the region your contract or regulator requires.
Routes
Pick your route.
Each pair has its own structural mismatch. These pages say what it is, in plain terms, before you talk to anyone.
Teams move for Fin and the Messenger, then discover four years of ticket history has to come with them.
Freshdesk teams outgrow ticket-first support and want a conversational inbox with an AI agent in front of it.
Help Scout mailboxes stop scaling once support needs routing, SLAs and an AI agent on the front line.
B2B teams supporting customers in shared Slack channels move to Pylon and need their Intercom history to come along.
Zendesk teams selling to enterprise customers switch to Pylon for Slack-native support and cannot leave four years of tickets behind.
Cost consolidation or an IT-led standardisation onto the Freshworks stack.
Growing teams outgrow shared mailboxes and standardise on Freshdesk for ticketing, SLAs and reporting.
Moving between platforms not listed here? We have almost certainly mapped the pair before - ask us.
Where we fit
Compared with the alternatives.
There are three other ways to do this. Each works - until the part it does not cover becomes your problem on go-live week.
| Criteria | DataGrine | Automated tools | CSV import | In-house |
|---|---|---|---|---|
| Records moved with threading intact | Yes | Yes | partial | Yes |
| Workflows, SLAs and views rebuilt | Yes | No | No | partial |
| Custom scripting for non-standard data | Yes | No | manual | costly |
| Sandbox dry run before go-live | Yes | partial | No | informal |
| Reconciliation against record counts | Yes | partial | manual | manual |
| Named engineer accountable at go-live | Yes | No | No | diverts staff |
| Runs inside your own cloud account | Yes | No | n/a | Yes |
| Fixed price agreed up front | Yes | per-job | hidden hours | variable |
Workflow rebuild applies where Intercom, Freshdesk or Pylon is the destination - the three platforms we implement. Moving somewhere else? We still move the records.
Questions
What teams ask before they commit.
How long does a migration take?
Most mid-sized desks move over a weekend. Calendar time is driven by API rate limits on the source platform and the volume of attachments, not by our end. We give you the estimate after the dry run, when we know the real numbers rather than the ones from the sales conversation.
Do we have downtime?
No. The bulk of the history moves while you keep working on the old platform. On cut-over day we run a delta sync for anything created since the bulk run, then switch the inbound channels over. The team stops working in one tool and starts in the other.
What happens to data that has no equivalent on the other side?
You get a written mapping document listing every object and field, what it becomes, and where the destination has no match. You decide the fallback - a custom attribute, a tag, a note appended to the conversation, or deliberately dropped. Nothing is decided silently.
Can we test before committing?
Yes. Every engagement includes a dry run into a sandbox or trial workspace on the destination. You open the records, check the ones you care about most, and sign off before the live run is scheduled.
Can the migration run inside our own cloud?
Yes. The engine can be deployed into your own AWS or Azure account, so customer data never leaves your infrastructure and never touches ours. This is usually what unblocks security review in regulated industries and under data-residency requirements.
How is it priced?
Fixed price, agreed before we start, based on record volume and the amount of workflow rebuild involved. Not hourly - the incentive should be to finish cleanly, not to stay longer.
Let’s move your data forward.
Tell us where you are moving from, where you are going, and roughly how many records. You will get a straight answer on what carries across, what has to be rebuilt, and what it costs - before you commit to anything.
- A written mapping document before anything moves
- A dry run you review in a sandbox
- Fixed price, agreed up front
- The workflows rebuilt too, where we implement