Migrate into Plain: where data lands, setup, limits
What Shuttio writes into Plain through its import, how it keeps the original dates and authors, why nothing is sent to a customer and the one thing Plain's Customer Inbox can still show, how to connect with the exact API key permissions, what the Plain API cannot do, and what a rollback leaves.
Last updated: 15 November 2026
Helpdesks that can move into Plain: Freshdesk, HubSpot Service Hub, Gorgias, Freshservice, Kustomer, Plain, Pylon, LiveAgent. A migration is free under 20,000 records in total: contacts, companies, deals, notes, activities and files together; otherwise it is priced by record count. The sample is free. See pricing. Plain to Plain is not offered. Plain also has importers of its own for some of these helpdesks.
Object by object: What objects are supported for Plain migrations.
Source by source: Plain support matrix.
Before you start
- Plain's import writes history and sends nothing to a customer: it starts no SLA clock, no auto-response and no workflow. Shuttio writes threads and messages only through that import and never calls a reply, an email, a chat or a thread-create call.
- One thing Plain documents and cannot switch off: an imported customer message and agent reply is stored as a custom timeline entry, and when Plain's Customer Inbox is enabled a customer who can open a thread can read it. Leave the Customer Inbox off for the import, or accept that customers can read their old threads. Internal notes are never shown there.
- Invite the agents in Plain first and Shuttio matches them by email: a reply or a note must be written by a Plain user. An agent with no Plain user is written by the workspace's first user, and the first line of the message names the original author. Shuttio never invites anyone.
- Label types, thread fields, account fields and customer groups are created on the way.
Connect
- Paste an API key from Plain under Settings, Machine users & agents (Add machine user, API User, Add API key). The key belongs to one workspace, so there is no address to type, and there is no OAuth and no app to install. The key is stored encrypted and deleted 14 days after the migration finishes. A migration is pinned to the workspace it first wrote to.
- Tick exactly these permissions when you create the key: thread:import, attachment:create, customer:create, customer:edit, customer:read, user:read, labelType:read, labelType:create, threadFieldSchema:read, threadFieldSchema:create, threadField:create, threadField:update, tenant:read, tenant:create, tenant:edit, tenantFieldSchema:read, tenantFieldSchema:create, tenantFieldSchema:update, tenantField:create, tenantField:update, customerTenantMembership:create, customerGroup:create, customerGroup:edit and note:create.
- Also tick, to allow a Cancel: thread:delete, customer:delete, tenant:delete and note:delete. Shuttio checks the key and its permissions before it saves anything.
What Shuttio writes
- A thread with its title, status (done when solved or closed, snoozed when pending), priority, assignee (matched by email), account, labels and thread fields, with its original created time.
- Every message, the first included, with its original time: a customer's as inbound, an agent's reply as outbound. The text is plain: HTML formatting is lost. A note is a note. Attachments are downloaded from the source and uploaded to Plain (up to 25 MB a message; Plain refuses exe, bat, msi, vbs, lnk and a few other types); a file that cannot be copied is named in its message.
- Custom fields as thread fields, named from the label and typed by the field (text, number, date, checkbox); owners as the owner's email in a text field.
- Every record carries an external id, so a retry never makes a second one.
Where each thing lands
| From | Object | Lands in Plain as |
|---|---|---|
| Freshdesk | Companies | Accounts |
| Freshdesk | Contacts | Customers |
| Freshdesk | Tickets | Threads, with their messages as imported inbound and outbound messages, notes, files and the original dates and authors (an agent with no Plain user of that email is named in the first line) |
| HubSpot Service Hub | Companies | Accounts |
| HubSpot Service Hub | Contacts | Customers |
| HubSpot Service Hub | Tickets | Threads, with their messages as imported inbound and outbound messages, notes, files and the original dates and authors (an agent with no Plain user of that email is named in the first line) |
| Gorgias | Customers | Customers |
| Gorgias | Tickets | Threads, with their messages as imported inbound and outbound messages, notes, files and the original dates and authors (an agent with no Plain user of that email is named in the first line) |
| Freshservice | Departments | Accounts |
| Freshservice | Requesters | Customers |
| Freshservice | Tickets | Threads, with their messages as imported inbound and outbound messages, notes, files and the original dates and authors (an agent with no Plain user of that email is named in the first line) |
| Kustomer | Companies | Accounts |
| Kustomer | Customers | Customers |
| Kustomer | Conversations | Threads, with their messages as imported inbound and outbound messages, notes, files and the original dates and authors (an agent with no Plain user of that email is named in the first line) |
| Plain | Accounts | Accounts |
| Plain | Customers | Customers |
| Plain | Threads | Threads, with their messages as imported inbound and outbound messages, notes, files and the original dates and authors (an agent with no Plain user of that email is named in the first line) |
| Pylon | Accounts | Accounts |
| Pylon | Contacts | Customers |
| Pylon | Issues | Threads, with their messages as imported inbound and outbound messages, notes, files and the original dates and authors (an agent with no Plain user of that email is named in the first line) |
| LiveAgent | Companies | Accounts |
| LiveAgent | Contacts | Customers |
| LiveAgent | Tickets | Threads, with their messages as imported inbound and outbound messages, notes, files and the original dates and authors (an agent with no Plain user of that email is named in the first line) |
Matching, and what is never changed
- A customer whose email, or an account whose external id, domain or name, Plain already has is linked to and never written or removed. A rollback does not remove it.
What the Plain API cannot do
- It lets an import write a message only as a user: an agent with no Plain user of that email is written by the workspace's first user.
- It holds one email per customer and has no phone, address, job title or custom field on a customer: they are one internal note on the customer. It has no created time to set on a customer or an account.
- It writes no satisfaction answer, no time entry and no SLA state: they are lines in the thread's closing note.
- Shuttio uses no call that deletes a label type, a thread field, an account field or a customer group: after a rollback the ones Shuttio created stay.
Not answered here? Email help@shuttio.com.