Zendesk to Plain Migration

MIGRATION OVERVIEW

Why teams migrate from Zendesk to Plain

The core problem

Migrating from Zendesk to Plain moves support data from a broad, enterprise-grade REST-based helpdesk to an API-first, GraphQL-native platform purpose-built for B2B engineering teams. Plain does ship a native Zendesk importer that handles end users, tickets, messages, and tags automatically, providing a fast path for standard migrations. However, fundamental data model mismatches — most critically the absence of a direct import path for Zendesk Organizations into Plain's Company and Tenant model, and the lack of custom ticket field mapping in the native importer — require additional API scripting or a managed service for anything beyond a basic migration. Attachments, organization-level custom fields, granular status mapping, and historical timestamp preservation all require custom engineering work against Plain's GraphQL API using mutations such as upsertCustomer, importThread, and importThreadMessages.

Why this matters for your migration

KEY CHALLENGES

What makes this migration complex

These are the architectural mismatches and technical hurdles specific to a Zendesk to Plain migration.

Most Critical

Organization to Tenant Mapping

Zendesk Organizations have no direct 1:1 equivalent in Plain; they must be decomposed into Plain's two-layer model of Companies (auto-assigned by email domain) and Tenants (representing product workspace or billing boundaries), requiring manual mapping logic before any migration code can run.

Blocks all downstream imports if mapped wrong

Custom Field Schema Translation

Zendesk custom ticket, user, and organization fields do not carry over through Plain's native importer and must be manually re-created as Thread Field schemas in Plain before API-based load scripts can populate them.

Status and Priority Model Mismatch

Zendesk's six-state ticket lifecycle (New, Open, Pending, On-hold, Solved, Closed) must be collapsed into Plain's three-state model (Todo, Done, Snoozed), requiring a deliberate mapping strategy that will inevitably lose granularity for pending and on-hold states.

Attachment Re-upload Complexity

Zendesk's CSV bulk export omits ticket comments and attachments entirely, meaning attachments must be fetched individually via the Zendesk REST API and re-uploaded through Plain's separate attachment upload flow, adding significant engineering complexity and latency to the migration.

API Rate Limit Constraints

Zendesk enforces strict rate limits as low as 200 requests per minute on Team-tier plans, and these limits apply simultaneously with Plain's own API constraints, requiring careful batching, cursor-based pagination, and retry logic to avoid data loss or migration stalls on large accounts.

Delta Sync During Cutover

The native Zendesk importer only syncs new records created after the initial import and does not propagate subsequent changes to existing tickets (status updates, reassignments, priority changes), meaning teams must plan a coordinated cutover window or build a custom delta sync mechanism to avoid data divergence.

MIGRATION RISK ASSESSMENT

Every migration risk, already solved

Migration between platforms is full of edge cases. Our engineers have identified every risk from Zendesk to Plain and built proven solutions for each one.

High complexity

Organizations / Companies & Tenants

Zendesk Organizations have no direct import path in Plain's native importer and must be manually decomposed into the Company and Tenant model, with organization-level custom fields requiring a completely separate migration strategy.

Solved
Custom Ticket Fields / Thread Fields

Custom field schemas must be manually re-created in Plain before migration, and the native importer does not carry over any custom field data, requiring full API-based scripting to populate Thread Fields from Zendesk source data.

Solved
Attachments

Attachments are excluded from Zendesk's bulk CSV export and must be individually fetched via the Zendesk REST API and re-uploaded through Plain's separate attachment upload flow, making this the most engineering-intensive entity to migrate correctly.

Solved
Macros / Automations / Triggers

Zendesk Macros, Triggers, and Automations have no automated migration path and must be manually reconstructed as Plain Workflows, Rules, and Auto-responders, requiring a full audit of existing automation logic before cutover.

Solved

Custom engineering

Ticket Comments / Thread Messages

Public and internal comments (notes) are imported by the native importer, but historical timestamp preservation and author attribution require API-based migration using importThreadMessages, and the CSV export path omits comments entirely.

Handled
Internal Notes

Internal notes on Zendesk tickets are imported by the native importer, but ensuring correct attribution and timestamp fidelity for historical internal notes requires API-based migration rather than relying solely on the built-in tool.

Handled
Knowledge Base / Help Center

Zendesk Guide content must be migrated separately to Plain's Help Center with no native import tool available, requiring manual export and reformatting of article content, though the absence of relational dependencies keeps risk lower than organization or custom field migration.

Handled

Clean transfer

Tickets / Threads

Core ticket-to-thread migration is well-supported by Plain's native Zendesk importer and the importThread GraphQL mutation, though very large accounts (500K+ tickets) may face extended migration windows of several hours.

Clean
End Users / Customers

Zendesk end-user records map cleanly to Plain Customers via the upsertCustomer mutation and are handled automatically by the native importer, making this one of the lowest-risk entities in the migration.

Clean
Tags / Labels

Zendesk ticket tags are automatically imported as Plain Labels by the native importer, representing one of the most straightforward entity translations in the migration.

Clean

What Our Customers Say

Real migration stories

Direct Review

“Fantastic at both guiding us through the process and helping us fix things as they come up and dial them in.”

Reviewed on G2

“The ease of the process and that ClonePartner was informing me what was going on at every step. If you're on the fence, do it. ClonePartner are great!”

Direct Review

“They were SO helpful. We had a few hiccups because our migration was in the middle of the process, but they were really flexible and did multiple delta migrations for us. We were able to map a lot of our old ticket data so it's usable for comparisons in the future.”

Direct Review

“Overall a great experience. We had to go back a few times to get everything just right, which was totally expected. The transition was smooth, and there was no data loss.”

Direct Review

“One of the easiest migrations I've ever been through. The team took care of everything — all our data, customer interactions and macros. The process was clear, straightforward and we felt supported all the way. An absolutely seamless experience for our support team and our customers.”

See all customer stories →

CUSTOM MIGRATION

Fully customizable engineer-led migration

Tailor your migration from Zendesk to Plain exactly to your needs with our flexible customization options. Our experts will configure the perfect migration plan for your business.

Migration Filters

Data Types

ZERO DOWNTIME

Your timeline. Our engineers.

A dedicated engineer runs your migration, planned around your schedule and your data.

No babysitting a wizard. Avoid debugging errors yourself.

Looking for a more detailed migration timeline?

Contact our team

Speed

The migration timeline depends on both our turnaround time and yours.

We can complete a migration in under a day when the accounts are connected and the sample migration is approved promptly.

Background Sync

We also support migrating the newest records first, so you can go live faster while the rest of the data is synced in the background.

Data Volume Impact

Larger data volumes may require longer migration windows.

Continuous Operation

Weekend migrations minimize disruption to your customer service operations.

MIGRATION TIMELINE

Your Zendesk to Plain migration, step by step

See how long your migration will take from start to finish. Drag the slider to estimate based on your data volume.

How many records are you migrating?

<10K 50K 100K 250K 500K 1M 2M 5M 10M+

Checklist ~3 days

Sample 1 day

Review ~2 days

Full 2 days

Delta 1 day

Your team ClonePartner

Estimated total

~9 business days

Migration Checklist

1 day · ClonePartner ~2 days · Your team

We prepare the optimal data mapping as a shareable spreadsheet. Your team reviews, approves, and adds any customizations.

Sample Migration

1 day · ClonePartner

We run a test migration with a representative sample of your data to verify mapping accuracy and identify any potential issues before the full run.

Review & Approve

~2 days · Your team

Your team reviews the sample migration results, confirms data accuracy and mapping, and gives the go-ahead for the full migration.

Full Migration

2 days · ClonePartner

We execute the complete migration of all your data to your new Plain, with real-time progress tracking and comprehensive logging.

Delta Migration

1 day · ClonePartner

We capture and transfer any new data that was added or updated during the main migration to ensure no data is lost. This final sync keeps everything current.

Pros and cons of different migration options

Choosing the right approach is key because migrating from Zendesk to Plain isn't just about moving data – it's about protecting customer relationships.

Feature / Criteria	ClonePartner	Automated Tools	CSV Import	In-house migration
Custom Scripting for complex data	✓ Engineers build & maintain	✗ No	⚠ Manual	✓ Yes – but costly
Sandbox & Pilot Migrations	✓ Full sandbox + pilot plans	⚠ Limited	✗ No	⚠ Often Informal
Manual validation & reconciliation	✓ Automated + manual QA	✗ No	✓ Yes (Manual)	✓ Heavy manual effort
Backup & rollback plan	✓ Robust procedures	✗ No	✗ No	⚠ Often incomplete
Handles automation and integrations	✓ Full support	⚠ Partial	✗ No	⚠ Possible but fragmented
Post-migration engineer support	✓ Dedicated engineers	✗ No	✗ No	⚠ Limited SLA
Adaptable to API changes	✓ Proactive adaptation	✗ No	⚠ Manual fixes	⚠ Slower response
Turnaround / SLA predictability	✓ Predictable SLAs	⚠ Fast but brittle	⚠ Slow and manual	⚠ Often slower
Data Security & Compliance	✓ High – enterprise grade	⚠ Medium (depends)	⚠ Low (manual)	⚠ Hidden gaps common
Pricing predictability	✓ Transparent & fixed	⚠ Low (per-job)	⚠ Low (manual hours)	⚠ High/variable OPEX
End-to-end project management	✓ Full E2E delivery & PM	✗ No	✗ No	⚠ Often partial
Business impact & opportunity cost	✓ No diversion of staff	✗ No	✗ No	⚠ Diverts engineering

What does an Engineer-led migration mean anyway?

Speed & Accuracy: Our Blended Method

We blend automation (smart scripts, bulk APIs) with human expertise for speed without risk. Our engineers manually check every mapping, validation, and exception.

You get:

Speed of automation for bulk record migration
Precision of engineers verifying integrity and business logic
Pilot migrations and sandbox testing to catch issues early
Real-time validation reports and rollback readiness

Result: 50x faster migrations than manual imports — with near-zero error rates.

Handling the Tricky Tech and API Details

The Zendesk and Plain APIs each behave differently, which is where our engineers shine. We build custom logic to handle the data quirks where generic tools typically break.

We handcraft API logic for:

Field mapping and transformation
Pagination, rate-limit handling, and throttling
Preserving conversation threads, attachments, and internal notes
Syncing custom fields, SLAs, and macros without breaking structure

Our scripts: Natively retry failed calls, re-queue large attachments, and ensure data parity.

No Guesswork

We don't just promise smooth migrations—we measure and prove them. Every client receives a Migration Validation Report with all metrics.

Typical results across projects:

100% record-count parity between your Zendesk data and Plain
Zero downtime during staged cutovers
99.9% attachment integrity (verified via checksum)
Full automation and preservation of all business rules

Our standard: Includes full SLA preservation and 48 hours of engineer-assigned support post go-live.

We Adapt to Your Setup (Not the Other Way Around)

No two teams configure Zendesk or Plain exactly the same way—with unique automations and data. We customize every migration script to fit your exact workflow, tags, and triggers.

Our engineers adapt for:

Custom fields, ticket forms, and workflows
Multi-brand or multi-language setups
Historical imports and partial (date-based) migrations
Integration re-mapping for CRMs, chat, or feedback tools

The promise: If your data doesn't fit a standard template, we build one just for you.

Enterprise-Grade Security & Compliance

Your customer data is precious. Our migration process maintains the highest standards of security and regulatory compliance.

SOC 2 Type II

Independently audited compliance with rigorous security standards

ISO 27001

Certified information security management system

GDPR

Full compliance with EU data protection regulations

HIPAA

Certified for handling protected health information

AES-256 Encryption

Bank-grade encryption for all stored credentials

Latest TLS

Secure transfer protocol for all data in transit

Role-Based Access

We follow role-based access control for every migration project

Scheduled Deletion

Automatic data purging after migration completion

FAQ

Frequently Asked Questions

Everything you need to know about migrating from Zendesk to Plain. Can't find what you're looking for? Talk to our team.

Does Plain have a built-in Zendesk importer?

Yes. Plain offers a native Zendesk importer under Settings → Zendesk importer. It imports end users as Customers, tickets as Threads, all messages (including internal notes), and ticket tags as Labels. After the initial import, it auto-syncs new data. However, it does not import custom fields, organizations, or satisfaction ratings, and changes to existing Zendesk tickets (status, priority, assignee) do not keep syncing.

How do Zendesk ticket statuses map to Plain?

Zendesk uses six statuses (New, Open, Pending, On-hold, Solved, Closed). Plain has three: Todo, Done, and Snoozed. New/Open map to Todo, Pending maps to Snoozed (Waiting for Customer), Solved/Closed map to Done. On-hold can map to either Todo or Snoozed depending on your team's semantics — these two Zendesk statuses are not operationally identical, so don't map them blindly to the same Plain state.

What data doesn't transfer from Zendesk to Plain?

Macros, triggers, automations, SLA policies, ticket forms, satisfaction ratings, audit logs, and Zendesk custom objects (Sunshine) have no migration path. They must be rebuilt manually or surfaced via Plain's Customer Cards and rule engine. Custom ticket fields also don't carry over through the native importer — you need API-based scripting with importThread for those.

How do Zendesk organizations map to Plain?

Plain has two organizational concepts: Companies (auto-assigned by customer email domain) and Tenants (which map to your product's workspace or org concept). Zendesk Organizations don't import directly via the native importer. Use Company for the business identity and Tenant when you need to model product workspaces. You'll need to create Tenants via the API and assign customers through scripting.

Do I need OAuth for a Zendesk API-based migration?

For new integrations, yes. Zendesk recommends OAuth and has announced that API tokens created in Admin Center will be permanently deactivated on April 30, 2027. If you're building a migration script now, use OAuth to avoid having to redo authentication later.

How long does the Zendesk to Plain migration take?

Most migrations complete within 1–5 business days, depending on data volume and complexity. We provide a detailed timeline after the initial assessment and can often complete small migrations in under 24 hours.

Will my team lose access to Zendesk during the migration?

No. Your source system remains fully operational throughout the entire migration. We run the migration in the background with zero downtime to your current operations.

Will there be downtime when migrating from Zendesk to Plain?

No. Our migration process is designed for zero downtime. We use a staged approach with background sync and a fast cutover, ensuring no disruption to your live business operations.

How do I validate that everything migrated correctly?

Every client receives a Migration Validation Report with comprehensive metrics including record-count parity, attachment integrity verification via checksum, and full audit logs. We also offer unlimited sample migrations so you can verify before committing.

Do I need professional help for this migration?

While simple migrations can sometimes be handled in-house, professional help ensures zero data loss, proper field mapping, and preservation of relationships between records. Our engineer-led approach catches edge cases that automated tools miss.

Does ClonePartner provide guidance before committing?

Yes. We provide a free consultation and assessment. We'll review your data structure, discuss your requirements, and provide a detailed migration plan and fixed-price quote before you commit to anything.

Still have questions?

Book a free 30-minute consultation with our migration engineers. We'll walk you through the exact approach for your Zendesk→Plain migration.

Contact our team

Ready to start your
Plain Migration?

Join hundreds of businesses who have successfully migrated with ClonePartner. Let's discuss your migration needs and build a plan that works for you.

Book free consultation

Attention to Detail

We meticulously handle every aspect of your migration, ensuring no data is lost during transfer and mapping every field correctly between platforms.

Custom Solutions

Every business is unique. We tailor your migration strategy to match your specific requirements, workflows, and data structures.

Security & Compliance

Your customer data is handled with enterprise-grade security protocols, ensuring compliance with GDPR, HIPAA, and industry standards.

Migrate from Zendesk to Plain with precision & ease

Why teams migrate from Zendesk to Plain