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

Migrate from Plain: what moves, permissions, limits

What Shuttio reads from Plain, where it lands in Zendesk Support, Gorgias, Freshdesk and 6 more, which permissions it needs and why, and what does not move.

Last updated: 15 November 2026

An API key. You paste a read-only machine-user key from Plain under Settings, Machine users & agents; the key belongs to one workspace and Shuttio reads that workspace only.

Object by object: What objects are supported for Plain migrations.

What Shuttio reads and moves

The list below describes the move into Attio. Where Clarify or Odoo differ, the destination's own article says so.

  • Accounts: As Zendesk organizations, matched by name: one Zendesk already has is linked to, never changed. The name, primary and alternate domains, tier and custom account fields are read.
  • Customers: As Zendesk end-users, matched by email: one Zendesk already has is linked to, never changed. The name, email, customer groups (as tags), accounts and assigned user are read.
  • Threads: Imported whole through Zendesk's ticket import with the original created time, status (done stays solved, snoozed is on hold), customer, assignee, priority, channel and labels. No customer is emailed and no trigger runs.
  • Messages and notes: Every email, chat message, Slack, Teams and Discord message, internal note and custom entry, in order, with its time and author (the customer or the matching agent).
  • Attachments: Downloaded from Plain through its temporary links and uploaded to Zendesk with the comment. A file that cannot be copied is named in the run's warnings.
  • Labels and thread fields: Labels as Zendesk tags. Each thread field is created in Zendesk when it has none of that name and type, and filled.
  • Satisfaction result, tier and external id: Kept as lines in the ticket's internal note: Zendesk has no field for them.

Where each thing lands

Plain objectIn Zendesk SupportIn GorgiasIn FreshdeskIn FreshserviceIn KustomerIn PlainIn PylonIn LiveAgentIn HubSpot Service Hub
AccountsOrganizationsA Company field on each customerCompaniesDepartmentsCompaniesAccountsAccountsCompaniesCompanies
CustomersEnd-usersCustomersContactsRequestersCustomersCustomersContactsContactsContacts
ThreadsTickets, with their replies, notes, files and original datesTickets, with their messages, notes, files and original datesTickets, with their messages as notes (an agent's are private), files, time entries and the original dates in custom fieldsTickets (incidents), with their messages as private notes, files and time entries; the original dates are in the notesConversations, with their messages, notes, files and the original dates and authors (when the key has the org.admin role)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)Issues with the original created date, and every message as an internal note with its files and the original author and time in its first line (Pylon sets no time or author on a note)Tickets, each with every message after the first as an internal note with its files and the original author and time in its first line (LiveAgent sets no time on a ticket or a note)Tickets, with their emails, notes, files and original dates

Notes, tasks, meetings, calls, files, owners and lists depend on the destination. This is the row for Plain, generated from the same tables the runner uses:

Into Zendesk Support

FromObjectsNotesTasksMeetingsCallsEmailsFilesOwnersLists
PlainAccounts, Customers, ThreadsNoNoNoNoNoYesYesNo

Into Gorgias

FromObjectsNotesTasksMeetingsCallsEmailsFilesOwnersLists
PlainAccounts, Customers, ThreadsNoNoNoNoNoYesYesNo

Into Freshdesk

FromObjectsNotesTasksMeetingsCallsEmailsFilesOwnersLists
PlainAccounts, Customers, ThreadsNoNoNoNoNoYesYesNo

Into Freshservice

FromObjectsNotesTasksMeetingsCallsEmailsFilesOwnersLists
PlainAccounts, Customers, ThreadsNoNoNoNoNoYesYesNo

Into Kustomer

FromObjectsNotesTasksMeetingsCallsEmailsFilesOwnersLists
PlainAccounts, Customers, ThreadsNoNoNoNoNoYesYesNo

Into Plain

FromObjectsNotesTasksMeetingsCallsEmailsFilesOwnersLists
PlainAccounts, Customers, ThreadsNoNoNoNoNoYesYesNo

Into Pylon

FromObjectsNotesTasksMeetingsCallsEmailsFilesOwnersLists
PlainAccounts, Customers, ThreadsNoNoNoNoNoYesYesNo

Into LiveAgent

FromObjectsNotesTasksMeetingsCallsEmailsFilesOwnersLists
PlainAccounts, Customers, ThreadsNoNoNoNoNoYesYesNo

Into HubSpot Service Hub

FromObjectsNotesTasksMeetingsCallsEmailsFilesOwnersLists
PlainAccounts, Customers, ThreadsNoNoNoNoNoYesYesNo

Each destination's own article says how its data is written: Zendesk Support, Gorgias, Freshdesk, Freshservice, Kustomer, Plain, Pylon, LiveAgent, HubSpot Service Hub.

Permissions and why

WhatWhy Shuttio needs it
A machine-user API keyCreate it in Plain under Settings, Machine users & agents, Add machine user (API User), then Add API key. The key belongs to one workspace, so no address is needed, and Shuttio sends it to Plain's API host only.
These permissionsTick thread:read, timeline:read, customer:read, user:read, labelType:read, threadFieldSchema:read, tenant:read and attachment:download (they cannot be changed later). Optional: tier:read and tenantFieldSchema:read. Shuttio checks the key and its permissions before it saves anything, and never writes to Plain as a source.

Plain documents no request limit; a large workspace takes hours, and the run pauses when Plain asks it to slow down until you resume it. The key is stored encrypted and deleted 14 days after the migration finishes. You can delete it at any time in Plain under Settings, Machine users & agents.

Known limits

  • System events: Status, assignment, label, priority and SLA changes are timeline events, not messages. They are counted in the run summary and stay in Plain.
  • Tiers, SLA policies, snippets and the help center: They are Plain settings or content, not records Zendesk's ticket import takes.
  • Speed: Plain documents no request limit. Shuttio keeps three calls in flight, waits when Plain asks it to and pauses the run when the wait does not clear; Resume carries on.
  • Emails: Shuttio reads no emails from this source.

Not answered here? Email help@shuttio.com.