Top Thena Alternatives (2026): Features, TCO & Migration

Top Thena Alternatives (2026): Features, TCO & Migration

Teams searching for Thena alternatives are typically hitting one of four triggers: pricing tier jumps as ticket volume grows, a need to support channels beyond Slack, tighter integration requirements with engineering tools like Jira or Linear, or concerns about the platform's long-term trajectory.

Many teams start with Thena but run into friction as they scale—pricing drifts from actual usage, some workflows push you out of Slack into a web app, and promised AI features arrive slowly. Multiple sources corroborate that users began seeking replacements around March 2026.

This guide compares the strongest alternatives on architecture, real pricing, migration complexity, and honest trade-offs.

Disclosure: ClonePartner is a migration services firm that executes helpdesk data migrations professionally. Where we note first-hand observations on API behavior or failure modes, those reflect migrations we've run. Vendor claims are sourced separately.

Where Thena Fits—and Where It Doesn't

Thena is an AI-native B2B customer support platform built around Slack and Microsoft Teams as primary support channels. It unifies customer messages into organized tickets from various channels, lets users leverage AI for autonomous support tasks like responding, applying fields, creating tickets, and escalating issues, and supports automation of workflows blending human and AI actions.

Thena built its reputation on turning messy Slack Connect channels into structured B2B ticketing. It excels at parsing conversational context, applying AI triage, and routing issues without forcing customers out of their native chat environment. Customers include Vercel, Amplitude, FOX, Etsy, and LaunchDarkly.

Thena's pricing tiers (2026):

Annual-only billing, no monthly option. Thena's public documentation doesn't explicitly state whether tickets are throttled, additional charges apply, or the account requires an immediate upgrade when exceeding the 1,000 ticket cap.

Thena's API: Standard tier rate limit is 60 requests per minute per user, org, and IP. Enterprise tier gets custom limits. Authentication uses an x-api-key header. API keys are generated from Dashboard → Organization Settings → Security and Access.

SLA configurability: Thena supports SLA policies on Standard tier and above, with breach escalation via Slack notifications. Multi-timezone SLA windows require manual configuration per account. No public documentation specifies a cap on the number of concurrent SLA policies.

Data retention post-cancellation: Thena has not published a formal data retention window. Before canceling, obtain written confirmation of: (1) the API access window post-cancellation, (2) how long ticket data persists, and (3) whether Slack attachment URLs remain valid during that window. As of March 2026, users have reported the service may be sunsetting, though the company has not issued a formal statement.

Before you leave: Check your renewal date and any auto-renewal clauses. Resolve or export open tickets before terminating API access.

The 7 Best Thena Alternatives in 2026

1. Pylon—Closest Slack-Native Match for External B2B

Best for: B2B SaaS teams supporting customers via Slack Connect at scale.

Pylon is an AI-native B2B customer support platform that unifies ticketing, Slack and Microsoft Teams support, email, chat widgets, knowledge bases, AI agents, and account intelligence in one workspace. Both Pylon and Thena map Issues to Accounts and rely on conversation threading. Pylon's data model is optimized for account-level intelligence, aggregating telemetry from Salesforce, HubSpot, and product databases to surface churn risks directly in the support view.

Pricing:

Two of Pylon's most valuable modules—Account Intelligence and AI—are sold separately. AI Assistants cost approximately $50/seat/month (3-seat minimum) and AI Agents run ~$100/month plus per-ticket usage, on top of the base plan. When factoring in AI add-ons, channel gating, seat minimums, and billing, actual cost can reach 2–3x the advertised price.

SLA configurability: Pylon supports multiple SLA policies assignable by account tier, with breach notifications via Slack DM or channel alert. Multi-timezone SLA windows are configurable at the account level.

Uptime commitment: Pylon publishes a 99.9% uptime SLA. Check status.pylon.com for historical incident data before signing.

User permissions: Pylon supports role-based access with Admin, Agent, and Viewer tiers. Viewer seats are free. Multi-org access (supporting multiple customer orgs from one Pylon workspace) is supported natively—a differentiator from Thena's single-org model on lower tiers.

Data residency: Pylon stores data in US-based AWS infrastructure. EU data residency is not publicly documented as of August 2026; confirm before signing if GDPR jurisdiction is a constraint.

Mobile: Pylon has no dedicated mobile app. Slack-based workflows are accessible via the Slack mobile app; the Pylon web UI is not mobile-optimized.

Why pick Pylon over Thena:

• Broader channel coverage (Slack, Teams, Email, Chat, Portal, Discord, WhatsApp, Telegram)
• Account Intelligence with health scores and churn signals
• Founded in 2022 out of Y Combinator, backed by a16z and Bain Capital Ventures, 750+ paying customers
• Pylon offers assisted migration from Thena, including tickets, attachments, and knowledge base articles

Watch out for:

• Pylon's Issues endpoint has a 10 rpm rate limit—a real constraint for custom integrations and bulk operations
• No BYOA or custom AI agent support—teams are limited to Pylon's built-in AI
• The public pricing URL now routes to a demo request, signaling a more sales-led process

Migration path from Thena: Moving from Thena to Pylon is structurally the easiest migration on this list because both platforms understand Slack thread context natively. Tickets migrate in a closed state—you can't reply to them from Pylon. Resolve active tickets in Thena before go-live.

The migration still requires an API-to-API pipeline: extract Thena tickets via the /v2/tickets endpoint with cursor-based pagination, ensure Slack user IDs align between systems (otherwise historical messages appear attributed to a generic "System" user), and push structured payloads into Pylon's API.

Loading into Pylon: Pylon's REST API accepts issue creation via POST /v1/issues. Pagination on the load side is not a concern for single-record writes, but implement retry logic with exponential backoff on 429 responses. The 10 rpm limit on the Issues endpoint means loading 50,000 tickets takes a minimum of 83 hours at sustained throughput; batch non-critical metadata in separate calls to maximize effective throughput.

For a deeper dive on Pylon's competitive position, see our Top Pylon Alternatives guide.

2. Plain—API-First for Engineering-Heavy Teams

Best for: Technical B2B SaaS teams that want programmable support infrastructure.

Plain offers deep Slack integration with native bi-directional channels, per-channel SLAs, emoji-based ticket creation, and real-time thread visibility, plus an API-first architecture with GraphQL, no rate limits, MCP server support, and Bring Your Own Agent.

Pricing:

Ari AI agent is included on every plan—no per-resolution surprises. However, as of July 2026, Plain's AI assistant Sidekick is metered through a monthly credit allowance, making AI costs harder to predict. Viewer seats are free.

SLA configurability: Plain supports per-channel SLA configuration—a differentiator from most alternatives, which apply SLAs at the inbox or tier level. Breach escalation is configurable per channel. Multi-timezone SLA windows are supported.

Uptime commitment: Plain publishes a 99.9% uptime SLA on Horizon and Frontier plans. Foundation plan SLA terms are not publicly specified.

User permissions: Plain supports Admin, Member, and Viewer roles. Viewer seats are free on all plans. BYOA (Bring Your Own Agent) requires Horizon or above. Fine-grained API key scoping (read-only, write-only, scoped by resource type) is available.

Data residency: Plain stores data in EU-based infrastructure (AWS EU West), making it a stronger default choice for GDPR-constrained teams than most alternatives on this list.

Mobile: Plain has no dedicated mobile app. The web UI is responsive but not designed for mobile-first workflows.

GraphQL API example: Plain's mutation for creating a thread (the equivalent of a Thena ticket) uses the following structure:

mutation CreateThread($input: CreateThreadInput!) {
  createThread(input: $input) {
    thread {
      id
      title
      status
      customer {
        id
        email
      }
    }
    error {
      message
      code
    }
  }
}

The absence of rate limits on Plain's side is the key advantage for large migrations—throughput is limited only by your extraction speed from Thena (60 rpm) and your transform layer capacity.

Why pick Plain over Thena:

• Fully public GraphQL API with no rate limits—the same API Plain uses internally
• Multi-channel: Slack, Teams, Discord, Email, Help Center, In-app Forms, Live Chat
• MCP server and BYOA support for teams building custom AI agents
• Native integrations with Linear, GitHub, Jira, incident.io
• EU data residency by default

Watch out for:

• The most useful features sit on higher tiers, and credit-based Sidekick pricing makes monthly AI cost harder to predict
• Smaller ecosystem than Zendesk or Intercom—fewer marketplace integrations
• Microsoft Teams support starts on Horizon; advanced security and BYOA live higher still
• CSAT collection is manual or API-driven—no built-in survey tool comparable to Zendesk's CSAT workflow

Migration path from Thena: No native Thena importer. Plain documents importers for Zendesk, Freshdesk, Intercom, Front, and Help Scout—but not Thena. Use Thena's REST API (60 rpm) to extract tickets, contacts, and accounts, then load via Plain's GraphQL API. The lack of rate limits on Plain's side is a genuine advantage—the bottleneck is always Thena's extraction speed. Budget 1–2 weeks for a mid-size dataset (5K–50K tickets).

3. Front—Email-First Shared Inbox

Best for: Teams pivoting away from Slack-native support toward email-centric collaborative operations.

Front approaches customer support from an entirely different angle. It is fundamentally an email-first shared inbox that has evolved into a customer operations platform. If your team wants to centralize email, SMS, WhatsApp, and live chat into a single workspace, Front (or one of the top Front alternatives) is the logical pivot.

Front's architecture is based on Conversations and Inboxes. A Conversation can contain multiple message types—an email thread that transitions into an internal comment thread, for example. Unlike Thena, which forces a ticketing structure onto chat, Front forces a collaborative inbox structure onto all channels.

Pricing:

Copilot is $20/seat/month unless included in Enterprise. Autopilot starts at $0.05 per conversation. Extra API capacity is a $200/month add-on per additional 100 rpm. Onboarding packages are required for contracts over $25k.

SLA configurability: Front supports SLA policies on Professional and above, with configurable breach thresholds and escalation routing. Per-inbox SLA configuration is supported; per-channel SLA (as in Plain) is not. Multi-timezone SLA windows require custom rule configuration.

Uptime commitment: Front publishes a 99.9% uptime SLA on Professional and above. Starter plan has no published SLA commitment.

User permissions: Front uses a role-based model with Admin, Team Manager, and Agent tiers. Workspace-level and inbox-level permissions can be configured independently. Guest access (read-only external collaborators) is available on Professional and above.

Data residency: Front offers US and EU data residency on Enterprise plans. Lower tiers default to US infrastructure.

Mobile: Front has native iOS and Android apps with full conversation management, including push notifications, internal comments, and assignment. This is one of Front's stronger differentiators for on-call support teams.

CSAT: Front includes built-in CSAT surveys on Professional and above, triggered automatically after conversation resolution. Historical CSAT scores export via API.

Why pick Front over Thena:

• Native iOS and Android apps for mobile-first or on-call teams
• Built-in CSAT survey tool with historical reporting
• Consolidates email, SMS, WhatsApp, and chat into a single collaborative workspace
• Well-documented REST API with predictable rate limits (50 rpm Starter, 100 Professional, 200 Enterprise)
• EU data residency available on Enterprise

Watch out for:

• If your core motion is account-centric Slack support, Front's email-first bias works against you
• Copilot AI is a $20/seat add-on—not included in base pricing
• Onboarding packages required for contracts over $25k add to first-year TCO

Migration path from Thena: This migration introduces significant data transformation challenges:

1. Flattening threads: Thena's Slack threads must be converted into Front Conversations. A single Thena ticket (which might represent 50 back-and-forth Slack messages) needs to be formatted into an HTML block or appended as sequential comments to maintain readability.
2. Identity resolution: Thena tracks users via Slack IDs. Front tracks users via email addresses. Your ETL pipeline must resolve U12345678 into jane.doe@client.com via your CRM or Slack workspace data. If this mapping fails, you lose attribution.
3. API constraints: Batch your imports and implement exponential backoff against Front's rate limits (100 rpm on Professional).
4. CSAT migration: Historical CSAT scores from Thena can be imported as custom conversation attributes in Front, but Front's survey logic will not retroactively apply to imported conversations.

For more on this data model pairing, see our guide on Front to Thena Migration: A Technical Guide.

4. ClearFeed—Bridge Between Slack and Your Existing Helpdesk

Best for: Teams that want Slack-native triage but use Zendesk, Jira, or Salesforce as the system of record.

ClearFeed ($24/agent/month or $40/month usage-based) is the only tool covering both internal and external support, with SLAs, AI, omnichannel intake, and native two-way sync to Zendesk, Salesforce, HubSpot, and Jira.

Pricing:

The usage-based model is unusual in this space and can be significantly cheaper for teams with few agents but many channels.

SLA configurability: ClearFeed inherits SLA configuration from the connected backend (Zendesk, Jira). SLA breach alerts surface in Slack. Native SLA policies (without a backend helpdesk) are limited.

Uptime commitment: ClearFeed does not publish a formal uptime SLA on its public pricing page. Confirm terms in contract negotiations.

User permissions: ClearFeed manages permissions at the Slack workspace level, inheriting Slack's channel membership model. Backend system permissions (Zendesk agent roles, Jira project permissions) are managed in those systems independently.

Data residency: ClearFeed stores data in US-based infrastructure. EU data residency is not publicly documented.

Mobile: ClearFeed operates through Slack, giving it full mobile capability via the Slack mobile app on iOS and Android. No separate ClearFeed mobile app exists.

CSAT: ClearFeed supports CSAT collection via Slack emoji reactions or dedicated survey messages. Scores sync to the connected backend helpdesk.

Why pick ClearFeed over Thena:

• Cheaper entry point ($24 vs. $29, and more feature-complete at that price)
• Converts conversations from multiple Slack channels into a single shared queue with SLAs and service-level metrics
• True two-way sync: Slack conversations create and update tickets in Zendesk/Jira in real time
• Works for both internal (IT, Ops) and external (customer) support
• Mobile via Slack—no separate app required

Watch out for:

• ClearFeed is strongest as a Slack layer on top of another system—if you want a standalone helpdesk, you still need a backend tool
• Fewer advanced features than Pylon or Thena for teams needing deep account intelligence or omnichannel beyond Slack
• Custom pricing on higher tiers requires a sales conversation
• No published uptime SLA

Migration path from Thena: ClearFeed doesn't import historical Thena tickets natively. Export from Thena via API, import into your target helpdesk (Zendesk, Jira), and let ClearFeed sit as the Slack layer. This is the cleanest migration path if you're also consolidating onto a traditional helpdesk.

5. Unthread—Purpose-Built for Internal Support

Best for: IT, HR, Finance, Legal, and Ops teams managing internal employee requests.

Unthread is a Slack-native internal helpdesk that turns Slack conversations into tracked, routed, and resolved tickets automatically. The target buyer is a support or IT operations leader at a company of 200 to 2,000 employees where multiple internal teams need to manage incoming requests without separate portals.

Pricing:

14-day free trial available.

SLA configurability: Unthread supports SLA policies per channel or queue, with Slack-based breach alerts. Multi-timezone SLA windows are configurable. The number of concurrent SLA policies is not publicly capped.

Uptime commitment: Unthread does not publish a formal uptime SLA on its public pricing page.

User permissions: Unthread uses Admin, Agent, and Requester roles. Requester access (employees submitting requests) does not require a paid seat. Only agents handling tickets consume the per-seat license.

Data residency: Unthread stores data in US-based infrastructure. No EU data residency option is publicly documented.

Mobile: Unthread operates through Slack, providing mobile access via the Slack mobile app. No separate Unthread mobile app.

CSAT: Unthread supports post-resolution CSAT collection via Slack, with reporting in the Unthread dashboard.

Why pick Unthread over Thena (for internal support):

• Reports automatic resolution of up to 40% of incoming tickets in a documented customer example
• Converts channels like #it-help or #hr-requests into structured support queues
• Bidirectional ticket sync with existing helpdesk platforms
• Purpose-built AI agents for internal workflows (IT provisioning, HR FAQ, ops requests)
• Requester (employee) seats are free—only agents are billed

Watch out for:

• No Slack Connect workflow—not designed for external customer support
• 5-seat minimum means $250/mo floor regardless of team size
• Conversation caps, Teams limitations, and beta API can constrain larger deployments
• No published uptime SLA

Migration path from Thena: Extract via Thena API, transform ticket schema to match Unthread's internal-focused data model. Thena's Account→Contact hierarchy doesn't map cleanly to Unthread's employee-centric model—budget extra time for field mapping. Internal notes and escalation threads require explicit flagging as private during the transform step.

6. Zendesk—Enterprise-Grade Omnichannel

Best for: Teams moving upmarket, signing enterprise SLAs, and requiring rigid ITIL-compliant routing or specific compliance certifications.

Zendesk's strength is extensibility through the Sunshine platform, combined with comprehensive reporting, advanced workflow automation, and compliance certifications including SOC 2, ISO 27001, HIPAA, and FedRAMP. No other platform on this list matches Zendesk's compliance coverage—for healthcare, government, or financial services buyers, this is frequently the deciding factor.

Zendesk uses a strict Ticket → Requester → Assignee relational model. It is schema-driven and relies on Custom Objects for extensibility. Zendesk's native Slack integration functions as a notification and ticket-creation layer—not a conversational interface like Thena's.

Pricing: Suite Team starts around $55/agent/mo; Professional at $115/agent/mo; Enterprise via sales. AI capabilities require separate add-ons ($50+/seat), pushing total cost of ownership to an average of $115/user/month at full feature set. Copilot is $50/agent/month, and AI agents are billed on automated resolutions.

SLA configurability: Zendesk supports unlimited SLA policies on Professional and above, with configurable breach escalation, multi-timezone business hours, and per-ticket SLA overrides. This is the most configurable SLA system on this list. SLA reporting is built into Explore (Zendesk's analytics layer) at no additional cost on Professional.

Uptime commitment: Zendesk publishes a 99.9% uptime SLA on Suite Team and above, with 99.95% available on Enterprise contracts. Financial penalty clauses for SLA breach are negotiable on Enterprise.

User permissions: Zendesk supports granular role-based access control with custom roles on Professional and above. Light agents (free read-only seats for internal stakeholders) are available on Team and above. Multi-brand support (serving multiple customer segments from one Zendesk instance) is available on Professional.

Data residency: Zendesk offers US, EU, and AU data residency on Enterprise plans. Lower tiers default to US infrastructure.

Mobile: Zendesk has native iOS and Android apps with full ticket management, push notifications, and offline read access. This is a strong mobile offering relative to Slack-native alternatives.

CSAT: Zendesk includes built-in CSAT surveys on all Suite plans, with configurable trigger conditions, survey templates, and Explore-based reporting. Historical CSAT scores are queryable via API.

Why pick Zendesk over Thena:

• Compliance certifications Thena can't match (HIPAA, FedRAMP, ISO 27001)
• Unlimited SLA policies with the most configurable breach logic on this list
• Massive integration ecosystem (1,500+ marketplace apps)
• Proven at enterprise scale (100K+ ticket volumes)
• Deep reporting via Explore; native CSAT included
• EU and AU data residency on Enterprise
• Native mobile apps (iOS and Android)

Watch out for:

• In 95 conversations with Zendesk customers evaluating alternatives, the #1 frustration was the inability to support customers natively in Slack. Slack is a notification bridge, not a native channel
• Base licensing is deceptive—budget for a 30–40% premium over base costs once you add AI, Premium Sandbox, and marketplace apps
• Configuration complexity: triggers, macros, and custom fields layered across admin UI require dedicated admin resources

Migration path from Thena: This is a high-friction migration. You are moving from an unstructured, conversational data model to a highly structured, relational database.

// Transforming Thena Slack context for Zendesk Ticket Import API
{
  "ticket": {
    "subject": "Historical Thena Ticket: Login Issue",
    "comment": {
      "html_body": "<b>Slack Thread Context:</b><br/>User: I cannot log in.<br/>Agent: Have you cleared your cache?",
      "author_id": 123456789
    },
    "custom_fields": [
      {"id": 987654, "value": "thena_migrated"},
      {"id": 123987, "value": "C01ABCDEF"}
    ]
  }
}

Key hurdles:

• Ticket comments: Use the Ticket Import API endpoint (/api/v2/imports/tickets.json) to set historical timestamps (created_at) when posting sequential conversation history.
• Tag limits: Zendesk limits tags per ticket. If your Thena instance relies on automated AI tagging, consolidate before loading.
• Thread flattening: Slack thread context degrades when loaded into Zendesk's comment model. Format thread history as a structured HTML block to preserve readability.
• CSAT migration: Historical Thena CSAT scores can be imported as custom ticket fields. Zendesk's built-in CSAT survey logic does not retroactively apply to imported tickets.
• Account mapping: Thena Accounts map to Zendesk Organizations. Map Thena account IDs to Zendesk organization IDs before loading tickets, or all imported tickets will appear unassociated.

For broader helpdesk migration strategies, see our Help Desk Migration Alternatives guide.

7. Intercom—AI Chat and Per-Resolution Pricing

Best for: Product-led growth companies that want AI-first ticket deflection and in-app messaging.

Salesforce is acquiring Intercom (now Fin) for $3.6B. This acquisition changes the long-term calculus—Intercom's roadmap will increasingly align with Salesforce's ecosystem, and standalone Intercom pricing and packaging may shift materially within 12–24 months of deal close. Teams evaluating Intercom should factor roadmap uncertainty into a longer contract negotiation.

Pricing: Essential at $29/seat/mo. Advanced at $85/seat/mo. Expert at $132/seat/mo. Intercom charges $0.99 per resolved outcome for Fin AI, while competitors use flat monthly fees. Per-resolution pricing gets more expensive exactly as success scales—a team deflecting 10,000 tickets/month via Fin AI pays $9,900/month in AI fees alone, on top of base seat costs.

SLA configurability: Intercom supports SLA policies on Advanced and above, with configurable response time targets and breach alerts. SLA reporting is available in the Reporting section. Multi-timezone business hours are supported. SLA policy count is not publicly capped.

Uptime commitment: Intercom publishes a 99.9% uptime SLA. Historical incident data is available at status.intercom.com.

User permissions: Intercom uses Admin, Teammate, and Collaborator roles. Collaborator seats are free read-only access for stakeholders. Workspace-level and inbox-level permission scoping is available on Advanced and above.

Data residency: Intercom offers US and EU data residency. EU residency is available on Advanced and above; confirm current availability given the Salesforce acquisition may affect infrastructure decisions.

Mobile: Intercom has native iOS and Android apps with full conversation management. Push notifications are supported. This is comparable to Zendesk's mobile offering.

CSAT: Intercom includes built-in CSAT surveys (called Conversation Ratings) on all plans. Survey triggers are configurable. Historical CSAT data exports via API.

Why pick Intercom over Thena:

• Strongest in-app messaging and product tour capabilities on this list
• Fin AI has documented high autonomous resolution rates for well-documented products
• Native iOS and Android mobile apps
• EU data residency available
• Built-in CSAT (Conversation Ratings) included on all plans

Watch out for:

• Per-resolution AI pricing is unpredictable at high volume—model your ticket deflection rate before signing
• Salesforce acquisition creates roadmap uncertainty; avoid long-term contracts without exit clauses
• Slack support is bolted on, not native
• The full cost model—outcomes + Copilot seats + channel usage—requires explicit modeling; buyers who skip that math underestimate TCO significantly

Migration path from Thena: Intercom documents a structured import flow: create/import contacts first, create custom data attributes second, then import conversations or tickets. The key design choice is whether historical data lands as tickets, conversations, or a split model. Note that conversation data exported to S3 does not include transcripts; transcripts require API or UI retrieval. Historical CSAT scores from Thena should be mapped to custom conversation attributes, as Intercom's Conversation Ratings will not retroactively apply.

Pricing Comparison Table

How to Export Data from Thena

Before committing to an alternative, confirm you can actually get your data out. Thena does not offer a one-click "Export All" button.

Thena's API suite covers authentication, SLA management, workflow orchestration, ticketing, accounts, teams, tags, forms, and comments.

Key extraction constraints:

• Rate limit: 60 requests per minute on Standard tier. For a dataset of 50,000 tickets with associated messages and metadata, expect 14–20 hours of extraction time at sustained throughput.
• No bulk export: Thena requires API-based extraction—paginate through tickets, then fetch associated messages, contacts, and accounts separately.
• Slack context resolution: Thena relies on Slack's infrastructure for message storage. When you query a ticket via API, you often receive pointers to Slack threads rather than raw conversation text. Your ETL pipeline must authenticate against both the Thena API and the Slack API simultaneously, joining ticket metadata with the Slack conversations.replies payload.
• Attachment handling: Attachments need separate download calls. Slack attachment URLs expire—download files during extraction or lose them permanently.
• Pagination: Implement cursor-based pagination. When the rate limit is hit, the API returns 429 Too Many Requests. Respect the Retry-After header and resume without duplicating data.
• Internal notes: Thena separates customer-facing messages from internal notes. When mapping to a new system, your payload must explicitly flag these as private. Failing to do so exposes historical internal chatter to customers the next time they reply to an old thread.
• CSAT data: Thena CSAT scores are accessible via the tickets endpoint as a field on the ticket object. Survey configuration and trigger logic are not exportable—these must be rebuilt in the target platform.
• Limited API access on lower tiers can create operational friction—confirm your tier's API access before planning extraction. Standard tier or above is required for programmatic export.

For a complete walkthrough, see our How to Export Data from Thena guide.

Migration Architecture: What Transfers and What Doesn't

There is no native migration path from Thena to any competing platform. Every migration requires a custom ETL pipeline.

Thena API (extract) → Transform layer → Target API (load)
     60 rpm              Field mapping       Varies by target
     Paginated            Schema transform    Rate limits vary
     x-api-key auth       Data validation     Auth varies

Estimated migration effort

These estimates include extraction, transform logic, load + retry handling, and QA validation. The dominant cost is always the transform layer—mapping Thena's Slack-threaded conversation model into whatever structure the target expects. AI configuration rebuild (routing rules, auto-responses, escalation logic) is typically 30–40% of total migration effort and is not included in these figures.

TCO Modeling: 10-Agent Team, 12-Month Projection

Real TCO goes beyond the sticker price. Here's what a 10-agent team actually pays over 12 months, including typical add-ons:

*ClearFeed TCO excludes backend helpdesk cost (Zendesk, Jira). Add $6,000–15,000/year for a 10-agent Zendesk Professional instance.

The biggest cost levers across these platforms are seat floors, AI metering, API limits, channel packaging, and services. The most expensive mistake is picking a platform that doesn't match your primary support channel—if most of your support starts in Slack Connect, a generic inbox tool creates hidden labor. If most of your work is email/web, paying a premium for Slack-centric architecture is equally wasteful.

Price the migration itself as part of platform cost. Pylon separates migration and implementation packages ($1,000 and $5,000). Zendesk sells launch services starting at $5,000–$30,000. Front requires onboarding above certain contract sizes.

Decision Framework

"We need to stay Slack-native for external B2B support" → Pylon (closest match) or Plain (if you need API extensibility or EU data residency)

"We want Slack as the interface but Zendesk/Jira as the system of record" → ClearFeed

"We're pivoting to email-first operations and need mobile support" → Front

"We're switching from external to internal support tooling" → Unthread

"We need enterprise compliance (HIPAA, FedRAMP) or the most configurable SLA system" → Zendesk

"We're product-led and want AI-first deflection with in-app messaging" → Intercom (but model the per-resolution costs and factor in Salesforce acquisition risk before signing a long contract)

"We want maximum API control and custom workflows" → Plain

"We need EU data residency by default without Enterprise pricing" → Plain

"We need native mobile apps for on-call coverage" → Front, Zendesk, or Intercom

What We've Seen Running Thena Migrations

We've executed Thena migrations across multiple target platforms. A few patterns:

The Account→Organization mapping is the hardest part. Thena's Account model carries metadata (health scores, custom fields, CRM sync data) that doesn't have a clean home in most targets. Flattening to tags loses queryability. Custom fields are the best compromise. For Zendesk specifically, map Thena Accounts to Zendesk Organizations and set the organization ID on every imported ticket before loading—otherwise tickets appear unassociated and CSAT reporting breaks.

Slack thread context degrades during migration. Thena stores conversations as threaded Slack messages with timestamps and sender metadata. When you load these into a non-Slack-native target (Zendesk, Intercom), the threading structure is lost. We preserve it by formatting thread history as a structured markdown block in the target's comment field.

Delta migrations are essential. Your team will keep using Thena during the migration window. Plan a final delta sync (new/updated tickets since the initial extraction) before cutover. Thena's API supports updated_after filtering, which makes this manageable.

AI configurations don't port. Thena's AI agents, auto-responses, and workflow rules are platform-specific. Budget time to rebuild these in your target—this is typically 30–40% of the total migration effort, and is separate from the data migration itself.

SLA policies require a full rebuild. No target platform imports Thena SLA configurations. Export your current SLA policy definitions (response times, breach conditions, escalation rules, business hours windows) as a separate documentation exercise before starting the migration. This is fastest to rebuild when documented in advance.

CSAT continuity requires explicit planning. Historical CSAT scores from Thena can be imported as custom fields on tickets in every target on this list. However, the survey trigger logic, survey templates, and in-flight surveys do not transfer. Plan a CSAT blackout period during migration and communicate it to stakeholders.

Open tickets need separate handling. Historical imports preserve content and metadata, but they do not preserve the live reply path for Slack, email, or Teams threads. Resolve active tickets in Thena before cutover, or plan a separate open-thread migration strategy.

User permission models require a full audit. Every target platform on this list has a different permission model from Thena. Export your current agent list with roles before migration, then map each role to the closest equivalent in the target. Light-agent or Viewer-equivalent roles in the target can reduce licensing costs.

Here's the 80/20 entity mapping between Thena and the most common targets:

{
  "thena_ticket": ["plain_thread", "pylon_issue", "front_conversation", "zendesk_ticket", "intercom_ticket_or_conversation"],
  "thena_account": ["plain_company", "pylon_account", "front_account", "zendesk_organization", "intercom_company"],
  "thena_contact": ["customer_or_contact_in_target"],
  "thena_internal_thread": ["internal_note", "comment", "side_conversation"],
  "thena_slack_thread_url": ["custom_field_or_note"],
  "thena_csat_score": ["custom_ticket_field_in_target"],
  "thena_sla_policy": ["rebuild_manually_in_target"],
  "thena_agent_role": ["closest_equivalent_role_in_target"]
}

The hard part lives in the exceptions: merged contacts, inactive users, cross-channel threads, custom fields with drifting definitions, and open conversations that still need a real transport path after cutover.

For related migration walkthroughs, see:

• Thena to Podium Migration: The CTO's Technical Guide
• LiveChat vs Thena (2026): Architecture, TCO & Migration

Making the Switch

Switching support platforms looks simple on a slide deck and turns painful in execution. The ticket data moves, but the workflow knowledge—routing rules, escalation logic, SLA configurations, AI training data, CSAT survey configuration, and permission models—lives in the platform config, not the export.

The software cost is only half of the TCO equation. The other half is the migration itself: transforming Thena's Slack-threaded, account-centric data model into whatever structure the target expects, rebuilding AI workflows and SLA policies, auditing and remapping user permissions, and executing a delta sync to capture changes made during the migration window.

If your team has the engineering bandwidth, a DIY migration using Thena's API is doable for small datasets under 5,000 tickets. For anything above 10,000 tickets, or if you can't pull engineers off product work for 2–4 weeks, an assisted migration pays for itself in time saved and context preserved.