Migrate from Thena to Kustomer with precision & ease

A seamless, customizable migration solution for moving your Thena data with perfect fidelity and minimal disruption.

Book free consultation

Last updated August 2026

Thena
Kustomer
MIGRATION OVERVIEW

Why teams migrate from Thena to Kustomer

The core problem
Migrating from Thena to Kustomer requires a fully custom API-based ETL pipeline, as no native migration path, CSV import with threading support, or third-party connector exists between these two platforms. Thena organizes support around a Slack-native Account → Contact → Request model with AI-generated metadata, while Kustomer anchors everything to a CRM-first Company → Customer → Conversation → Message hierarchy built around a unified customer timeline. The fundamental data model transformation requires resolving Slack user identities to email addresses, converting Slack mrkdwn to HTML, mapping Thena AI metadata to Kustomer custom attributes (Klasses), and enforcing strict parent-child import ordering. Platform logic including workflow automations, SLA definitions, routing rules, and AI agent configurations cannot be migrated via API and must be rebuilt manually in Kustomer.
Why this matters for your migration
KEY CHALLENGES

What makes this migration complex

These are the architectural mismatches and technical hurdles specific to a Thena to Kustomer migration.

Most Critical

Slack Identity Resolution

Thena message authors are often represented as Slack user IDs (e.g., U04ABCDE12) that must be resolved to email addresses via the Slack API before Messages can be attributed to Kustomer Customers or Users, and this resolution becomes non-recoverable if the Slack workspace or bot token is decommissioned before extraction completes.

Blocks all downstream imports if mapped wrong

Slack mrkdwn to HTML Conversion

All Thena messages originating from Slack use Slack's proprietary mrkdwn format rather than standard Markdown or HTML, requiring a custom conversion pipeline — including user mention substitution, link parsing, and block-level element handling — before message bodies can be loaded into Kustomer's timeline.

Strict Hierarchical Import Ordering

Kustomer enforces a non-negotiable parent-child creation sequence — Companies must exist before Customers, Customers before Conversations, and Conversations before Messages — meaning any deviation in pipeline ordering results in 422 Unprocessable Entity or 404 errors on parent references.

AI Metadata Schema Provisioning

Thena's AI-generated fields (title, summary, urgency, sentiment, category, tags, actionable) have no native equivalent in Kustomer and must be pre-configured as custom attributes on the Conversation Klass before any import begins, requiring schema design decisions prior to data load.

Dual-Side Rate Limit Management

Thena's standard tier enforces a 60 requests-per-minute limit per user, org, and IP — requiring queued, asynchronous extraction with exponential backoff across an estimated 10–14 hours of extraction time — while Kustomer imposes 300–2,000 rpm limits on the load side depending on plan tier.

Attachment Re-hosting Pipeline

Attachments cannot be referenced by their original Thena or Slack URLs in Kustomer; each file must be individually downloaded from the source, re-uploaded to Kustomer's storage via API, and then linked to its corresponding Kustomer Message object.

COMPLETE COVERAGE

Intelligent Human-Verified Data Mapping

Our migration engineer precisely maps every data point from Thena to Kustomer, ensuring perfect continuity for your customer support operations.

Thena
Kustomer
Conversations
Conversations
Messages
Messages
Customers
Customers
Contacts
Customers
Agents
Users (Agents)
Teams
Teams
Tags
Tags
Macros
Shortcuts (Macros)
SLA Policies
SLA Policies
Webhooks
Hooks (Webhooks)
Internal Notes
Notes
Attachments
Attachments
Knowledge Base Articles
Knowledge Base Articles
Custom Fields
Customer Custom Attributes
Kanban Boards
Searches (Views/Saved Searches)
Analytics Reports
Not Available

Looking for more entity mappings?

Contact our team
MIGRATION RISK ASSESSMENT

Every migration risk, already solved

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

High complexity
  • Messages and Replies
    Messages require Slack mrkdwn-to-HTML conversion, Slack user ID resolution, correct Conversation parent linkage, and per-request API calls that rapidly exhaust Thena's 60 rpm rate limit, making this the highest-complexity and highest-volume entity in the pipeline.
    Solved
  • Attachments
    Attachments require a three-step re-hosting process — download from Thena or Slack, re-upload to Kustomer, and re-link to the target Message — and Slack-hosted file URLs may expire or become inaccessible if the Slack workspace is decommissioned during migration.
    Solved
  • Platform Logic and Automations
    Workflow automations, SLA definitions, routing rules, AI agent configurations, and dashboard configurations are entirely non-migratable via API and must be fully rebuilt manually in Kustomer, representing significant post-migration engineering and configuration effort outside the ETL pipeline scope.
    Solved
Custom engineering
  • Contacts / Customers
    Email serves as the natural deduplication key, but Slack IDs stored on Contacts must be preserved as custom attributes and resolved to real identities before load, introducing risk of orphaned or misattributed customer records.
    Handled
  • Requests / Conversations
    The one-to-one Request-to-Conversation mapping is conceptually clean, but AI metadata fields must be pre-configured as Klass custom attributes in Kustomer before import, and the Conversation cannot be created until its parent Customer and Company already exist.
    Handled
  • Internal Notes / Thread Messages
    Each internal thread message must be mapped to a distinct Kustomer Note object to preserve author and timestamp fidelity, requiring careful differentiation between public replies and internal notes during the transform phase.
    Handled
  • AI Metadata
    All eight AI-generated fields (title, summary, tags, category, userDefinedTags, urgency, sentiment, actionable) are present in the Thena API response but have no native Kustomer equivalent and must be manually modeled as Conversation Klass custom attributes before data load begins.
    Handled
  • Custom Fields
    Thena custom field definitions retrieved from the /v3/custom-fields endpoint must be manually reviewed and recreated as Kustomer Klass attributes, as field types and validation rules differ between platforms and require schema design decisions before load.
    Handled
Clean transfer
  • Accounts / Companies
    Thena Accounts map 1:1 to Kustomer Companies with a straightforward domain name or external ID match, making this the most structurally simple entity in the migration.
    Clean
  • Tags
    Tags must be created in Kustomer before import and then referenced by ID during load, but this is a well-defined pre-migration step with low risk of data loss provided the tag creation phase is completed first.
    Clean
What Our Customers Say

Real migration stories

See all customer stories →
CUSTOM MIGRATION

Fully customizable engineer-led migration

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

Migration Filters

Conversation Type

Filter by chat, email, or social media conversations

Tag-Based Selection

Migrate tickets with specific tags only

User Selection

Migrate tickets for specific users or agents

Time Range

Migrate tickets from a specific time period

Data Types

Tickets & Conversations

Full conversation history with all metadata

Automations & Macros

Workflows, templates, and automation rules

Knowledge Base

Articles, categories, and help center content

Customer Profiles

Customer information and interaction history

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 Thena to Kustomer 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

1

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.

2

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.

3

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.

4

Full Migration

2 days · ClonePartner

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

5

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.

Related Guides

Pros and cons of different migration options

Choosing the right approach is key because migrating from Thena to Kustomer 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:

  1. Speed of automation for bulk record migration
  2. Precision of engineers verifying integrity and business logic
  3. Pilot migrations and sandbox testing to catch issues early
  4. 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 Thena and Kustomer 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:

  1. Field mapping and transformation
  2. Pagination, rate-limit handling, and throttling
  3. Preserving conversation threads, attachments, and internal notes
  4. 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:

  1. 100% record-count parity between your Thena data and Kustomer
  2. Zero downtime during staged cutovers
  3. 99.9% attachment integrity (verified via checksum)
  4. Full automation and preservation of all business rules
Our standard: Includes full SLA preservation and 30 days of engineer-assigned support post go-live.

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

No two teams configure Thena or Kustomer 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:

  1. Custom fields, ticket forms, and workflows
  2. Multi-brand or multi-language setups
  3. Historical imports and partial (date-based) migrations
  4. 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 Thena to Kustomer. Can't find what you're looking for? Talk to our team.

Is there a native migration tool from Thena to Kustomer?
No. There is no built-in connector, no CSV import that preserves conversation threading, and no third-party tool supporting Thena as a source and Kustomer as a target. You must build a custom API-based ETL pipeline using Thena's Platform API and Kustomer's REST API.
How do Thena objects map to Kustomer's data model?
Thena Accounts become Kustomer Companies. Thena Contacts become Kustomer Customers (deduplicated by email). Thena Requests become Kustomer Conversations with Messages nested underneath. AI metadata (title, summary, tags, urgency, sentiment) should be stored as custom attributes on the Kustomer Conversation Klass.
How do I handle rate limits when importing into Kustomer?
Include the importedAt field in every Conversation and Message payload. This bypasses Kustomer's per-customer object rate limit of 120 creations per minute. Your binding constraint becomes the global API rate limit, which ranges from 300 rpm (Professional) to 2,000 rpm (Ultimate).
What happens to Thena's AI-generated metadata during migration?
Thena's AI metadata (title, summary, category, urgency, sentiment, tags) has no native Kustomer equivalent. Define custom attributes on Kustomer's Conversation Klass before import using Kustomer's naming convention (Str, Txt, Bool suffixes), then populate them during the load phase.
How long does a Thena to Kustomer migration take?
Budget 84–136 engineer-hours and 2–4 weeks elapsed time for a mid-size dataset (10K–50K requests). The main time sinks are the transform layer (Slack mrkdwn conversion, identity resolution) and validation/QA. Extraction and loading are time-gated by API rate limits on both sides.
How long does the Thena to Kustomer 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 Thena 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 Thena to Kustomer?
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 Thena→Kustomer migration.

Contact our team

Ready to start your
Kustomer 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.