Migrate your Trengo data
Omnichannel shared inbox combining WhatsApp, email, live chat, voice, Instagram, and Facebook for mid-market support teams in eCommerce and hospitality.
In its favor
Why people choose Trengo
The signal that keeps Trengo on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Consolidates WhatsApp, email, Instagram, Messenger, voice, and live chat into one shared team inbox, eliminating tab-switching and missed messages.
Meta Business Partner status means official WhatsApp Business API access with approved message templates, reducing friction for eCommerce support teams.
Built-in AI Agent handles tier-1 ticket deflection automatically, claimed to reduce handling time significantly for repetitive queries.
Intuitive interface with fast handoffs between team members ensures no customer waits when agents are busy or offline.
Strong customer support reputation — reviewers specifically name support agents who made onboarding smooth and problem resolution fast.
Per-conversation billing introduced in 2024 charges per message thread within 7-day windows, which surprises teams used to flat-seat pricing and can inflate costs unpredictably.
AI Agent features with surcharges are gated behind higher tiers, leading to sticker shock when teams enable automation and see line-item charges on the invoice.
Limited integration ecosystem compared to established players like Zendesk — third-party CRM and ERP connectors require custom API work.
Lack of a transparent free trial means onboarding costs are sunk before full feature evaluation, causing churn when the fit is not right.
Reasons to switch
Why people leave Trengo
The recurring reasons buyers give for replacing Trengo. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Trengo fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Trengo pricing overview
Trengo charges per user on Boost and Pro plans (€25 and €40 respectively) with flat-rate options at €299 and €499/month. Since 2024, it also bills per conversation with 7-day rolling windows, topped up via a wallet system. AI Agent usage generates additional per-resolution surcharges. WhatsApp Business API fees are billed separately by Meta.
Boost
Tier 1 of 3
€25/user/month or €299/month flat
What's included
Need help selecting your Helpdesk?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Trengo's schedule — see our quote-based pricing →
What gets migrated
Trengo object support
Object-by-object support for Trengo migrations. Per-pair details surface during scoping.
Conversations
Fully supportedThe primary object in Trengo. Each conversation holds a 7-day rolling activity window. We export all conversation metadata, status, assignee, and channel. The 7-day window resets on any message activity, which affects how we chunk historical data during migration scoping.
Messages
Fully supportedMessages are nested inside conversations. We export all inbound, outbound, and internal notes with timestamps, sender attribution, and attachment references. Pagination is required for large threads.
Contacts
Mapping requiredStandard fields (name, email, phone) map cleanly. Custom contact properties vary by account and must be field-mapped to the destination schema. We handle type conversion for date, boolean, and multi-select custom fields.
Channels
Mapping requiredChannels (WhatsApp, email, Instagram, Facebook, live chat, voice, SMS) define the routing layer. Channel credentials and connection configs are exportable. We preserve which channel each conversation originated from and flag active vs. archived channels.
Teams
Fully supportedTeams and their member assignments are exported. Routing rules (which team handles which channel or inbox) are preserved as configuration data alongside the user roster.
Users
Fully supportedUser profiles including name, email, role, and active/inactive status are exported. Agent-level permissions and ownership of conversations are mapped to the destination user schema.
Knowledge Base Articles
Fully supportedArticles with body content, categories, and publication status are fully exportable. We map article-category hierarchy and any linked widget associations to the destination CMS.
Automation Workflows
Mapping requiredTrengo's workflow triggers and actions are configurable. We export workflow definitions as structured JSON where the API exposes them, but complex multi-step automations may require manual recreation in the destination platform.
Tags
Mapping requiredTags applied to conversations or contacts are exported as flat label arrays. Tag naming conventions differ across platforms, so we apply a naming map to avoid collision at the destination.
Reports and Stats
Mapping requiredAggregated reporting data (CSAT, response times, channel volumes) is exportable as CSV. Historical report snapshots do not carry forward SLA and performance thresholds, which must be reconfigured manually.
| Object | Support | Notes |
|---|---|---|
| Conversations | Fully supported | The primary object in Trengo. Each conversation holds a 7-day rolling activity window. We export all conversation metadata, status, assignee, and channel. The 7-day window resets on any message activity, which affects how we chunk historical data during migration scoping. |
| Messages | Fully supported | Messages are nested inside conversations. We export all inbound, outbound, and internal notes with timestamps, sender attribution, and attachment references. Pagination is required for large threads. |
| Contacts | Mapping required | Standard fields (name, email, phone) map cleanly. Custom contact properties vary by account and must be field-mapped to the destination schema. We handle type conversion for date, boolean, and multi-select custom fields. |
| Channels | Mapping required | Channels (WhatsApp, email, Instagram, Facebook, live chat, voice, SMS) define the routing layer. Channel credentials and connection configs are exportable. We preserve which channel each conversation originated from and flag active vs. archived channels. |
| Teams | Fully supported | Teams and their member assignments are exported. Routing rules (which team handles which channel or inbox) are preserved as configuration data alongside the user roster. |
| Users | Fully supported | User profiles including name, email, role, and active/inactive status are exported. Agent-level permissions and ownership of conversations are mapped to the destination user schema. |
| Knowledge Base Articles | Fully supported | Articles with body content, categories, and publication status are fully exportable. We map article-category hierarchy and any linked widget associations to the destination CMS. |
| Automation Workflows | Mapping required | Trengo's workflow triggers and actions are configurable. We export workflow definitions as structured JSON where the API exposes them, but complex multi-step automations may require manual recreation in the destination platform. |
| Tags | Mapping required | Tags applied to conversations or contacts are exported as flat label arrays. Tag naming conventions differ across platforms, so we apply a naming map to avoid collision at the destination. |
| Reports and Stats | Mapping required | Aggregated reporting data (CSAT, response times, channel volumes) is exportable as CSV. Historical report snapshots do not carry forward SLA and performance thresholds, which must be reconfigured manually. |
Gotchas
What to watch for in Trengo migrations
Issues we've hit on past Trengo migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Conversation-based billing model is migration-critical
7-day conversation window resets on any activity
AI billing is a separate surcharge line item
No documented bulk export endpoint requires pagination strategy
| Severity | Issue |
|---|---|
| High | Conversation-based billing model is migration-critical |
| Medium | 7-day conversation window resets on any activity |
| Medium | AI billing is a separate surcharge line item |
| Low | No documented bulk export endpoint requires pagination strategy |
Leaving Trengo?
Where Trengo customers move next
7 destinations Trengo can migrate to.
How a Trengo migration works
Four steps, Trengo-specific
Connect
Bearer token authentication using a personal access token. The token is passed in the Authorization header as 'Bearer {token}' alongside JSON content-type headers. into Trengo. Scopes limited to read-only on the data we move.
Map
We translate Trengo-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Trengo quirks before production.
Migrate
Full migration with Trengo rate-limit handling. Rollback available throughout.
FAQ
Trengo migration FAQ
Answers to the questions buyers ask most during Trengo migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Trengo migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther helpdesks we support
Ready when you are
Migrate Trengo.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Trengo setup and destination — written quote back within a business day.