Done-for-you migrations are open: our consultants run yours. See the migration service

What we touch, and what we keep.

A migration reads your entire customer history out of one system and writes it into another. That is worth a page of specifics rather than a badge, so here are the mechanisms, the subprocessors, and the disclosure most tools leave out.

3
sample values per CSV column reach a model
12
subprocessors, listed with their data and location
5
kinds of data with a stated deletion time

How your data is held

OAuth, not pasted credentials

Attio, HubSpot, Pipedrive and Zoho CRM all connect over OAuth with scoped, revocable tokens — revoke us from your own admin and we are out, no ticket required. Affinity has no OAuth, so it takes an API key, and an Attio API key is offered only as a clearly-marked fallback. Clarify takes a workspace slug and a Personal API key, and Odoo takes an API key, an import package you load yourself, or our Odoo app. Every connection belongs to one migration, and its token is deleted 14 days after the migration finishes. Zoho CRM asks for read-only permissions only, and its refresh token is revoked at Zoho, in the data centre that issued it, when we delete it.

Tokens encrypted with a key we do not store beside them

Every credential is sealed under its own data key, which is itself wrapped by a master key held outside the database. One module in the codebase can decrypt, and one table holds token material. A database dump on its own opens nothing.

Background jobs carry an id and nothing else

The durable job that runs your migration receives a single migration id. Credentials and records are fetched inside the job, from encrypted storage, and never travel through a queue payload, a log line or a dashboard. Secrets and personal data are never logged at all.

Every request re-checks who owns the row

Ownership is enforced at the data layer on each request rather than in the page that renders it, and a migration belonging to someone else answers the same way one that does not exist does — so an id cannot be probed for.

Your CSV is deleted when the full run finishes

A CSV imports in full, with no sample, and the file is kept encrypted while it waits and runs, then removed when the import finishes or you roll it back; a paused or failed run keeps it until you resume, retry or roll back. A CSV sample started before CSV imports ran in full keeps its file for up to 30 days, and a daily sweep deletes it after that. What we keep is the structure the run used, the field mapping, the id map and the provenance ledger — the bookkeeping that makes a re-run idempotent and a rollback complete. Not your rows. The one exception is the Fields step's field list with up to three example values per field, encrypted, used for at most 24 hours and deleted within 48 hours by a daily purge. It is read from your source and your destination.

Reconnecting to a different Attio workspace stops the run

Every id we hold is scoped to one workspace. If the connected workspace changes, resume, retry, full-run and rollback are all refused at the door rather than writing this migration's records into somebody else's Attio.

What reaches Claude, exactly

Shuttio uses a model in two places: to guess the type of each column in a CSV you upload, and in the help chat. This is the whole of what it receives.

What the model sees

A CSV you upload, and only a little of it: each column's name, at most three sample values, each truncated to 80 characters, and, for a column with 25 or fewer distinct values, how many there are. Those sample values are record values from your file. That is what lets it tell an email column from a date or a fixed list of choices. A connected CRM sends it nothing.

What the help chat sees

The help chat sends Claude our product documentation, the messages you type in it (up to 20 turns), and, on a migration page, a summary of that migration: its state, source and destination, the options chosen, each object's counts and status, and error groups by object, kind and field. Never a record value, name, email, source id, error text or API response. We store each question you type and the answer you got for 12 months, to answer follow-ups and improve the help content; a visitor who is not signed in is identified by a random id in their browser. Our team gets a Telegram alert with the first question of each conversation. The text of earlier turns comes back from your browser and is used as context only; it is never stored from there and never reaches another account.

What the model never sees

The import itself, and the rows of your CRM. The only record values it can see are the CSV column samples above. Nothing designs your structure with a model — it is mirrored from your CRM's own schema by code — and the writer never calls one. The records of a migration stream from your source into your destination without passing through Claude, whether you are moving fifty rows or five million.

Values that could not be written, kept 14 days

When a single value could not be written to your destination (a malformed email, a number that is not a number), the migration's Errors tab lists it with the object, the field, the source record's id, our own explanation, the destination's error code and HTTP status, and up to 200 characters of the value. The destination's error message is never stored. The value is deleted 14 days after the migration finishes, at the same time as its credentials; the rest of the line stays with the migration.

What the model can decide

Nothing, on its own. It guesses the type of each column in a CSV you upload; you see every guess on the field review and can change it before a single write reaches your destination. The help chat only answers questions and changes nothing.

Connecting an AI assistant

Claude, Cursor or another MCP client can start a migration for you through our MCP server. This is what it can reach.

A token you make and can revoke

You create a token on the MCP access page of your account; it is shown once. We store only its SHA-256 hash, never the token. Revoke it there and the next call is refused. A token stops working when its owner leaves the organization. Up to 10 live tokens per person per organization.

Or sign in from the assistant

Claude or ChatGPT can open Shuttio in your browser instead of taking a token. You sign in here and press Allow on a page that names the app and where your answer goes; an app that registered itself is marked as unverified. You can allow reading only. The app gets an access token that lasts one hour and a refresh token that is replaced at every use; we store only their SHA-256 hashes. A refresh token used twice ends the connection. An app unused for 30 days has to ask again. Disconnect any app on the MCP access page, and its next call is refused. Up to 20 connected apps per person per organization.

It does what the web app does, and less

Sixteen tools. Nine run the migration: list the systems, list your migrations, start a draft migration, read its status, list the objects, run the free sample, read the report, start the full run and roll back. Seven set it up before the sample: read the setup, choose the objects, list and change an object's fields, list the fields a filter can use, set a filter and change the options; they change the migration's setup in Shuttio and nothing in your CRMs. Connecting a CRM happens only in your browser, so your CRM credentials never pass through the assistant. The free sample starts when the assistant calls it: it writes a capped number of test records, and a rollback removes them. A paid full run returns a Stripe payment link for you to open; it starts after you pay, and the assistant never sees a card. A full run with nothing to pay, and every rollback, start only after you open a page of the web app, signed in, read what the step will do and paste the code shown there into the chat; the assistant cannot read or make that code, and a wrong code is refused after five tries.

What the assistant receives

Counts per object, the migration's state and links, and the sample or run report: up to 25 skipped records per object with their source id and the reason. When it lists an object's fields it also receives each field's name and one sample value of up to 80 characters, as the Fields step shows them. The assistant is yours: its vendor, not Shuttio, processes what it reads, under your agreement with them.

Limits

60 calls a minute per token. 30 refused tokens from one IP address lock it out for 15 minutes.

Five things that are never kept longer than we say

For any reason, on any plan, at any record count.

Your record rows

Never leaves

The mirror and the writer are code, with no model in either. Records stream from your CRM into your destination without passing through one.

Your uploaded CSV

Deleted on finish

Deleted when the import finishes or you roll back; a paused or failed run keeps it until you resume, retry or roll back. A CSV imports in full, with no sample. What we keep is the structure, the mapping, the id map and the provenance ledger — not your rows.

Your Odoo import package

Deleted within 7 days

An import package is kept encrypted and deleted 7 days after it is built, or when you finish the load guide, whichever comes first. Its download links work for 24 hours, and only for you.

Your records on the way to the Odoo app

Deleted within 24 h

If you use our Odoo app, the records waiting for your Odoo are kept encrypted, and deleted as soon as your Odoo confirms them, and after 24 hours at most. The app's access is stored only as a fingerprint, and you can disconnect it from Odoo or from Shuttio at any time.

Credentials

Deleted after 14 days

Sealed under a per-record data key wrapped by a master key held outside the database, and never placed in a job payload, a log line or a dashboard, and deleted 14 days after the migration finishes (revoked with the provider where it allows).

Who else processes it

The full list. Shuttio is operated by VentuRise LLC, Wyoming, USA.

VercelApplication hosting
NeonPostgres database
AnthropicClaude, for CSV column types and the help chat, described above
Amazon Web ServicesThe server that runs migrations and its job queue; records pass through, none are stored
ResendCompletion emails, when enabled
StripePayment for a CRM migration into Clarify, Odoo, HubSpot, Pipedrive, Breakcold, Twenty, Capsule, HighLevel, ActiveCampaign, Zendesk Sell, OnePageCRM, Cloze, Pipeline CRM, Less Annoying CRM, Close, Copper, Keap, Affinity, Freshsales, Insightly, Zoho CRM, SoftSync, Zendesk Support, Gorgias, Freshdesk, Freshservice, Kustomer, Plain, Pylon, LiveAgent, HubSpot Service Hub, folk, Ashby, Lever, Greenhouse, ClickUp, Asana or Trello; receives billing details, no records
GoogleSign-in only, via OAuth
PostHogProduct analytics on the EU cloud; receives page views and flow steps by internal user id, no records, credentials or cookies
IPinfoLooks up the network owner of a visitor's IP address on our website; receives the IP address, returns the organisation and country
TelegramAlerts to our team when a help chat conversation starts or an answer fails; receives the page, the first question and a signed-in user's email, no records
RB2BFor visitors in the United States, may match a visit to a business profile; receives the visit; never loaded outside the United States
XMeasures our ads on X: tells us how many people who saw or clicked an ad then visited or signed up.

Getting back to where you were

Cancelling a migration deletes every record, note, task, meeting, list entry, attribute and select option that migration created, in reverse order, working from a ledger written as each one was made. A record the migration matched and updated in place stays, and the values it overwrote are not restored. Everything else that was in your workspace beforehand is never touched.

Custom objects the migration created are deleted too, last, once its own records are gone and the object is empty. One that holds records the migration did not create (yours, or another migration's) is left in place and named, with its record count. Attio's standard objects and any object you already had are never touched. One thing a rollback leaves in place is the lists it created: Attio's API cannot delete a list. They are listed for you by name at the end of a rollback rather than quietly left behind, so the cleanup is a few clicks in Attio and not a discovery six months later.

Read it, forward it, then start with a free sample.

Nothing is written to your new CRM until you have reviewed the objects and fields, and every CRM migration starts as a free sample: 5% of your companies, contacts or deals, 10 to 1,000 records, picked at random, with their linked records.