Assisted data portability
We move your data
out of a SaaS tool.
Switching tools usually stalls in the same place: the years of history sitting inside the old one. So we do that part for you. Our team extracts your data from the product you're leaving and loads it into its replacement — typically a self-hosted open-source alternative, running on your own server.
What we move
The destination is usually something from our catalog, but it doesn't have to be — it can be a tool you already run.
Messaging
Channels, threads and file attachments out of Slack and into a self-hosted alternative such as Mattermost.
CRM
Contacts, companies, deals and activity history out of your current CRM and into an open-source one such as EspoCRM.
Databases
A managed database moved onto your own Postgres instance, with the schema and the data brought across together.
Files
Documents and shared folders out of Dropbox or Google Drive and into something you host yourself, like Nextcloud.
Replacement tools are examples, not commitments — the right one is decided with you. Running something that isn't on this list? It's still worth asking.
How it actually works
Four steps, and the old tool stays switched on for all of them.
01
We check what's possible
What you're on now, what the destination needs, and what the source tool's export actually includes. You get the "won't come across" list up front.
02
We pull the data
Using whatever export the source tool offers — its own export feature or its API — and reshape it for the destination.
03
We load it and you check it
It goes into the new tool on your server. You compare it against the old system, and we adjust until it matches.
04
You cut over when you're ready
You keep the old tool running until you're satisfied. Nothing gets canceled on our say-so.
What you have to do
It isn't nothing. Here's the honest list, so it isn't a surprise halfway through.
Trigger the export, or give us access you control
Most products only let an owner or admin run a full export. Either you run it and hand us the archive, or you grant access that you can revoke the moment we're done.
Tell us what matters
Which channels, which objects, which years. "All of it" is usually both more expensive and less useful than a list somebody has actually thought about.
Check the result
You're the only person who knows whether the deal history looks right. We fix what doesn't, but you have to be the one to look.
Keep paying the old tool until you're done
Don't cancel on the strength of a promise. Cancel once you've looked at the data in the new place and it's right.
This, or a data migration?
Same team, same discipline, different scope. If you ask for the wrong one we'll tell you.
This page
Assisted data portability — the data
Getting years of history out of one product and into another. The destination can be a server with us, or a tool you already run somewhere else. Scoped to the data rather than the infrastructure.
The bigger job
Data migrations — the whole stack
Moving off usage-based billing or per-seat SaaS onto your own server: app, data and DNS, on a window agreed with you. Starts with a free savings number in writing.
See data migrationsFree
The scoping conversation
What you're on, what its export allows, what would survive the trip and what wouldn't. No charge, no card, and you can take that answer and do the move yourself.
Agreed up front
The work itself
Scoped and priced in writing before anything starts: what moves, what doesn't, and what it costs. Nothing about it is charged as a surprise afterwards.
If the destination is a server with us, it's priced like anyone else's: a flat monthly VPS tier from $4.99/mo to $89.99/mo, or a dedicated machine at $199/mo. Billed monthly in advance, and provisioned within 24 hours of your order.
What we're not claiming
- This is people, not a product. There is no one-click export button, no connector library and no migration dashboard. Our team does it by hand, which is the reason it works on tools nobody built an integration for.
- How much history comes across is your current provider's decision, not ours. What a source tool's export includes is set by that tool. We check it and tell you before you commit — not after.
- No fidelity guarantee. We won't promise that every attachment, reaction, thread and custom field survives a trip between two products that were never designed to talk to each other. We'll tell you which ones won't.
- No turnaround SLA. We don't publish a completion time; the window goes in your written scope. The only two timing commitments on this site are that servers are provisioned within 24 hours of an order and that we reply to messages within 48 hours.
- No customer stories. Olympia is new, so there are none to tell yet and none invented here.
The part we will commit to: once it's on your server, it's yours. Root access, your data, and you can take it somewhere else whenever you like — there's no exit fee and nothing here is designed to make leaving hard. That's the whole point of the service.
Ask what would survive the move
Tell us the tool you want to leave and where you'd like the data to land. The answer, including the parts that won't come across, costs you nothing.