Trengo to Zendesk migration
We migrate Conversations, Messages, Contacts, Teams, and Knowledge Base articles from Trengo into Zendesk with the conversation-to-ticket schema resolved upfront, channel routing context preserved as tags and custom fields, and the 7-day rolling window billing model accounted for before any records move.
FlitStack AI migrates tickets, ticket comments, end users, agents and groups from Trengo to Zendesk, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 3-5 weeks.

What moves from Trengo to Zendesk?
Moving from Trengo to Zendesk is a conversation-to-ticket remapping problem.
Read the full summary
Trengo organizes customer interactions as Conversations with nested Messages inside 7-day rolling activity windows; Zendesk uses Tickets with threaded Comments and a separate channel routing layer. We export full conversation threads including internal notes, contact profiles with custom fields, team rosters, and Knowledge Base articles, then map each Conversation to a Zendesk Ticket, each Message to a Comment, and each Trengo Channel to a Zendesk tag that preserves routing provenance. We do not migrate Trengo automation workflows, macros, or channel credentials as code; we deliver a written inventory of every workflow definition and channel configuration requiring manual recreation in Zendesk Admin. Billing runs are frozen during migration to prevent the 7-day conversation window from resetting mid-export, which would distort historical volume counts.
Conversation → Ticket
Each Trengo Conversation maps to one Zendesk Ticket.
How it maps
We preserve the original Trengo conversation ID in a custom field trengo_conversation_id__c for cross-reference and audit. Conversation status (open, resolved, pending) maps to Zendesk Ticket Status values; Trengo's custom status labels are recreated as Zendesk custom ticket statuses in the Admin settings before migration. The channel origin (WhatsApp, email, Instagram, Facebook, voice, live chat, SMS) is preserved as a tag with the prefix channel: (e.g., channel:whatsapp) so that routing provenance is queryable in Zendesk without a separate channel object.
Message → Ticket Comment
All Messages nested inside a Trengo Conversation (inbound customer messages, outbound agent replies, and internal notes) map to Zendesk Ticket Comments.
How it maps
We set the Comment author type (end-user vs agent vs internal) using Zendesk's Comment.author_type field and the public/private visibility flag. Message timestamps are preserved as Comment.created_at so the full chronological thread is intact in Zendesk. Attachment URLs are extracted from Message records and re-linked as Zendesk Ticket Attachments after ticket creation.
Contact → End User
Trengo Contacts map to Zendesk End Users.
How it maps
Standard fields (name, email, phone) map cleanly to Zendesk user.name, user.email, and user.phone. Custom contact properties (date, boolean, multi-select, text) are mapped to Zendesk custom user fields, applying type conversion (Trengo multi-select to Zendesk tag array, Trengo date to Zendesk date field). We resolve duplicate emails during import using Zendesk's duplicate detection so that existing Zendesk users are not over-written.
User (Agent) → Agent
Trengo User profiles (name, email, role, active/inactive status) map to Zendesk Agents.
How it maps
Agent-level permissions and conversation ownership are preserved as a mapping note for the customer's Zendesk admin to configure Group membership and role-based access manually post-migration. We export the full user roster with trengo_owner_id preserved in a custom field agent_trengo_id__c for reconciliation.
Team → Group
Trengo Teams with their member assignments map to Zendesk Groups.
How it maps
Routing rules (which team handles which channel or inbox) are exported as structured JSON and delivered as a configuration document alongside the migration. The customer recreates these as Zendesk Views and routing rules in Admin because routing logic is destination-platform-native and cannot be lifted from Trengo directly.
Channel → Tag (prefixed) + Integration reference
Trengo Channels (WhatsApp, email, Instagram, Facebook, voice, live chat, SMS) do not have a direct Zendesk equivalent as data objects.
How it maps
We capture channel assignments per Conversation and apply them as Zendesk Tags with the prefix channel: for reporting segmentation. Channel credentials (WhatsApp Business API tokens, email SMTP configs) are flagged in the discovery inventory as items requiring manual reconfiguration in Zendesk Admin under Channels.
- ConversationTicket1:1
- MessageTicket Comment1:1
- ContactEnd User1:1
- UserAgent1:1
- TeamGroup1:1
- ChannelTagtransformed
+ 4 more in the mapping below
How Trengo and Zendesk differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Trengo | Zendesk |
|---|---|---|
| Primary object model | Conversations with nested Messages and 7-day rolling activity windows | Tickets with threaded Comments and a separate channel routing layer |
| Channel routing | Channels (WhatsApp, email, Instagram, Facebook, voice, chat, SMS) are native objects with credentials | Channels handled via tag taxonomy and native integrations activated per channel type |
| Conversation billing | Per-conversation billing with 7-day rolling windows reset by any activity | Per-agent-seat pricing with no conversation-window concept |
| AI Agent billing | Separate surcharge line item per AI resolution event | Zendesk AI bundled under Service Suite tiers; pricing varies by edition |
| Knowledge base structure | Articles with categories and publication status; single-hierarchy CMS | Zendesk Guide with 5-level article hierarchy, sections, and categories; Enterprise tier adds subsections |
| Team structure | Teams with member assignments and channel routing rules | Groups with agent membership and views scoped per group |
| Reporting | Built-in analytics with CSAT, response time, and channel volume metrics | Zendesk Explore with custom dashboards, SLA tracking, and team performance metrics; Explore Pro required for advanced reporting |
What to watch for in a Trengo to Zendesk migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
7-day conversation window resets during migration freeze
Trengo's billing window resets on any message activity in a thread, including during a migration export run.
How we handle it
If agents continue responding to tickets while we are exporting Conversations, the 7-day rolling window resets and the same Conversation will appear in multiple billing periods. We freeze Trengo writes (read-only mode) during the export window and coordinate a cutover date with the customer's team so that no new activity is recorded in Trengo after the snapshot is taken. This prevents both billing distortion and duplicate conversation exports.
Trengo has no dedicated bulk export endpoint
The Trengo REST API exposes list endpoints with cursor-based pagination but no bulk export endpoint.
How we handle it
For migrations exceeding 5,000 Conversations or 50,000 Messages, we implement chunked date-bounded export slices with retry logic to stay within Trengo's rate limits. We avoid exporting during high-volume periods (business hours) to prevent rate limit hits that would extend the migration timeline. Large thread pagination is handled by iterating message pages per conversation to avoid timeout on single large requests.
Channel credentials do not migrate and must be reconfigured
Trengo Channel credentials (WhatsApp Business API tokens, Instagram/Facebook OAuth tokens, email SMTP credentials, voice SIP configurations) live in Trengo's platform and cannot be exported as migration data.
How we handle it
We document every active channel and its configuration details during discovery so the customer's Zendesk admin knows what to reconfigure in Zendesk Admin under Channels. WhatsApp Business API templates approved in Trengo are Meta-managed and may need re-approval for use in Zendesk's WhatsApp integration.
Zendesk Explore requires an upgraded tier for advanced reporting
Zendesk Explore (custom dashboards, SLA analytics, team performance metrics) is not included in the Suite Essential or Team tier.
How we handle it
Teams migrating from Trengo's built-in analytics that need Explore-level reporting must upgrade to Suite Professional or above. We flag this during scoping so the customer understands the reporting upgrade cost before committing to the migration timeline. Historical Trengo reporting data is delivered as a CSV snapshot that can be imported into Explore manually.
Internal notes in Trengo map to public Comments in Zendesk by default
Trengo distinguishes between customer-facing messages and internal agent notes within a Conversation.
How we handle it
Zendesk Comments have a public/private flag. We set internal notes to private Comments (author_type = agent, public = false) by default, but we flag this mapping for the customer's admin to review because Zendesk admins can still see private Comments under certain permission levels. The distinction between internal note and private Comment should be validated against the customer's Zendesk role configuration post-migration.
How the migration runs
Discovery and data audit
We run a full inventory of the Trengo account: Conversation count by status and channel, Message count with thread depth distribution, Contact count (standard fields and custom properties), User roster (active and inactive), Team structure, active Channel list, Knowledge Base article count and category hierarchy, and active workflow definitions.
What this step covers
We confirm Zendesk Guide is activated in the destination account before scoping begins. The discovery output is a written scope document with record counts, a custom field mapping table, and a channel reconfiguration checklist for the customer's admin.
Migration freeze and cutover planning
We coordinate a migration freeze window with the customer's Trengo team.
What this step covers
During this window, Trengo is set to read-only (no new Messages, no conversation status changes, no new Contacts created). We set a cutover date at least 48 hours after the freeze begins to capture any final delta. We also confirm that Zendesk's channel integrations (WhatsApp, Instagram, email routing) are pre-configured or queued for configuration so that customer-facing routing can resume without delay after cutover.
Schema pre-creation in Zendesk
Before any data moves, we create all required Zendesk custom fields, custom ticket statuses, Groups, and (if applicable) Guide Sections and Categories.
What this step covers
Custom contact properties from Trengo are pre-mapped to Zendesk custom user fields with type conversion applied. Tag naming conventions are finalized to avoid collision with Zendesk system tags. This schema phase runs in parallel with the final Trengo data export to minimize total project time.
Conversation and message migration
We export Trengo Conversations in date-bounded slices to manage pagination and avoid mid-window resets.
What this step covers
Each Conversation is inserted as a Zendesk Ticket with status, priority, assignee (resolved via email match against the User roster), and tags (including channel: prefix tags). Messages are then inserted as Comments using Zendesk's bulk comment endpoint, preserving author attribution, public/private visibility, and timestamps. Attachment URLs are re-uploaded as Zendesk Ticket Attachments after ticket creation using the Zendesk Attachments API.
Contact and agent migration
Trengo Contacts are inserted as Zendesk End Users using Zendesk's user import with duplicate detection by email.
What this step covers
Custom field values are mapped using the pre-created Zendesk custom user fields. Trengo Users are inserted as Zendesk Agents with their active/inactive status preserved; we flag any Trengo User without a matching email in the Zendesk org for the customer's admin to provision before or during the migration. Team-to-Group mapping is applied during user provisioning.
Knowledge Base and delta sync
Knowledge Base articles are migrated to Zendesk Guide in category and section hierarchy order.
What this step covers
Publication status is preserved (published articles go live immediately if Guide is active; draft articles remain in draft). A final delta sync captures any new Conversations, Messages, or Contacts created during the migration freeze window. We then deliver the automation and macro inventory document and the channel reconfiguration checklist to the customer's Zendesk admin for post-migration rebuild.
Validation and handoff
We validate migration completeness: Ticket count in Zendesk against Conversation count in Trengo, Comment count against Message count, User count against Contact count, and article count against Knowledge Base count.
What this step covers
We spot-check 25-50 random Tickets against the source Trengo threads for content accuracy. We deliver the migration completion report, the automation inventory document, the channel reconfiguration checklist, and the tag naming map. We do not rebuild workflows, macros, or SLA policies in Zendesk; these are handed off for the customer's admin to configure using the documentation provided.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with conversation volume, custom contact field count, and knowledge base article count. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Trengo to Zendesk →Why teams move from Trengo to Zendesk
- Zendesk's integration ecosystem dramatically outpaces Trengo's. With over 1,800 marketplace listings versus Trengo's limited third-party connector set, Zendesk connects natively to Salesforce, Jira, SAP, NetSuite, and ERP systems that Trengo teams require custom API work to reach. Reviewers cite the lack of native CRM and ERP connectors as the primary friction point driving the switch.
- Zendesk Explore provides custom dashboards, SLA tracking, and multi-dimensional team performance metrics that Trengo's built-in analytics cannot match. Teams managing complex SLAs across enterprise accounts migrate to Zendesk specifically for the reporting depth and the ability to slice metrics by channel, agent, group, and time period without exporting to a data warehouse.
- Trengo's 2024 shift to per-conversation billing with 7-day rolling windows introduced unpredictable cost spikes that surprise mid-market teams. Every active thread reset by inbound or outbound messages inflates the monthly conversation count against wallet caps. Zendesk's per-agent-seat pricing is predictable regardless of conversation volume, which reviewers cite as a direct financial reason to switch once teams understand their actual Trengo usage.
- Zendesk is the established industry standard for enterprise and mid-market support operations. Teams that need to recruit agents with prior helpdesk experience find that Zendesk proficiency is expected, whereas Trengo requires onboarding from scratch. Additionally, SOC 2 Type II, ISO 27001, and enterprise procurement compliance requirements are more readily met with Zendesk's documented security posture and enterprise support tiers.
- Zendesk's workflow and macro ecosystem, while not migratable as code, offers far greater depth for complex automation patterns (SLA escalation, conditional routing, multi-step business rules) than Trengo's workflow triggers. Teams that have outgrown Trengo's automation primitives cite the need for Zendesk's more expressive rule engine as a structural reason for the switch, independent of feature parity at the surface level.
Questions, answered
Trengo to Zendesk migration questions
How long does a Trengo to Zendesk migration take?
Most migrations land between three and five weeks for accounts under 5,000 Conversations and no complex knowledge base structure. Migrations with large engagement histories (over 100,000 messages), 500+ Knowledge Base articles, or multi-channel routing rules requiring detailed tag mapping move to eight to fourteen weeks because of thread-chunking strategy, channel-to-tag mapping, and Knowledge Base hierarchy recreation. The migration freeze window itself is typically 48-72 hours; longer freezes indicate scope gaps identified during discovery.
Do Trengo automation workflows and macros migrate to Zendesk?
No. Trengo workflow triggers and actions are not migratable as code. We export workflow definitions as structured JSON and deliver a written inventory that documents each workflow's trigger conditions, actions, delays, and recipient rules alongside a recommended Zendesk Trigger or Automation equivalent. The customer's Zendesk admin rebuilds these manually in Zendesk Admin post-migration. Macros (canned response templates) similarly do not migrate; we recommend rebuilding them in Zendesk Macros using the exported content as a reference. This is standard scope because workflow and macro structures are destination-platform-native.
Will our conversation history and internal notes come through intact?
Yes. We migrate the full conversation thread including customer-facing messages and internal agent notes. Internal notes are inserted as Zendesk private Comments (public = false). We preserve timestamps, author attribution, and attachment references. The original Trengo conversation ID is stored in a custom field trengo_conversation_id__c on each Zendesk Ticket for cross-reference. Channel origin (WhatsApp, email, Instagram, etc.) is preserved as a prefixed tag for reporting segmentation in Zendesk Explore.
What happens to our Trengo Knowledge Base articles?
Knowledge Base articles migrate to Zendesk Guide with category and section hierarchy preserved. Publication status is maintained (published articles are live in Guide; drafts remain drafts). We store the original Trengo article ID in a custom field on each Zendesk article. Zendesk Guide must be activated in the destination account before article import; we confirm this during scoping. Zendesk Guide's 5-level article subsection hierarchy is available on Enterprise plans; Standard plans support a 2-level structure (Section and Category), which may require flattening Trengo's deeper hierarchies.
How do we handle WhatsApp Business API credentials and channel routing?
Channel credentials (WhatsApp Business API tokens, Instagram OAuth, email SMTP, voice SIP) cannot be exported from Trengo and must be reconfigured in Zendesk Admin. We document every active Trengo channel and its configuration details during discovery and deliver a channel reconfiguration checklist so the customer's admin knows exactly what to set up in Zendesk. WhatsApp Business API message templates approved in Trengo are Meta-managed and may require re-submission for Zendesk's WhatsApp integration. Channel routing rules (which team handles which channel) are delivered as a structured document for manual recreation in Zendesk Views.
Will Zendesk Explore reporting work for our migrated data?
Yes, but the tier matters. Zendesk Explore custom dashboards and SLA analytics require Suite Professional or higher; they are not included in Suite Essential or Team. We migrate all ticket data with timestamps, assignee, status, and tags so that Explore reporting works immediately on migrated data. Historical Trengo reporting metrics (CSAT, response times, channel volumes) are delivered as a CSV snapshot that the customer's admin can import into Explore manually or use to validate pre-built Explore report templates. SLA policies from Trengo do not migrate as Zendesk SLA definitions; they are documented for manual recreation.
Can FlitStack AI also migrate from Zendesk back to Trengo if the switch does not work?
Yes. We offer reverse migration from Zendesk to Trengo as a separate scope. The reverse migration follows the same dependency order (Contacts, Users, Teams, Conversations, Messages, Knowledge Base) with Zendesk's data model mapped back to Trengo's conversation-centric structure. Note that Zendesk ticket IDs will not map back to Trengo conversation IDs without a custom field storing the Zendesk ID on each record. We recommend maintaining the migration field mapping document as a reference regardless of direction.
Related migrations
Sources: official documentation
- About ticket import — Zendesk help
- How can I bulk update users — Zendesk help
- About custom objects — Zendesk help
- Bulk importing user data with the data importer — Zendesk help
- How do I format the date field in Sell — Zendesk help
- About custom ticket fields — Zendesk help
- About lookup relationship fields — Zendesk help
Get a quote
Moving from Trengo to Zendesk?
Tell us roughly how many records and objects you have. We scope the mapping and the Zendesk setup with you, then send a quote.
Get a quote