Thena to LiveChat Migration

MIGRATION OVERVIEW

Why teams migrate from Thena to LiveChat

The core problem

Migrating from Thena to LiveChat is an entirely API-driven process with no native import path, no CSV connector, and no third-party tool that supports Thena as a source. Thena organizes support around Slack-centric Requests with threaded messages, AI-generated metadata, and a B2B account model, while LiveChat's async ticketing backend (HelpDesk) uses a flat, chronologically ordered array of typed events per ticket. Historical Thena data must be transformed and loaded into HelpDesk via POST /v1/importedTickets, not LiveChat directly, requiring custom engineering to resolve Slack user identities, convert Slack mrkdwn to HTML, and restructure threaded conversations into HelpDesk's event model. Thena workflows, Slack routing rules, AI agent configurations, and CSAT feedback have no import path and must be redesigned from scratch.

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 LiveChat migration.

Most Critical

Slack User Identity Resolution

Thena messages reference Slack user IDs rather than email addresses, requiring a lookup against the Slack API to resolve each sender's email and display name before constructing HelpDesk requester and agent fields.

Blocks all downstream imports if mapped wrong

Slack Markup to HTML Conversion

Thena conversation content uses Slack's mrkdwn format, which must be programmatically converted to HTML before insertion into HelpDesk's message events, as HelpDesk does not parse or render mrkdwn natively.

Threaded Conversation Flattening

Thena stores messages in Slack-style threads with nested replies, while HelpDesk requires a single flat, chronologically ordered array of typed events, necessitating custom logic to merge and sort threaded content.

Attachment Transaction Expiry

HelpDesk's 3-step attachment upload flow uses transaction IDs that expire after 24 hours, and any partially failed upload requires the entire transaction to be abandoned and restarted from scratch, adding complexity to large-scale attachment migrations.

Silent Agent Authorship Corruption

HelpDesk silently treats messages as requester-authored when agentID is omitted, meaning incorrectly mapped agent messages produce no API error and require explicit post-load validation to detect.

Thena Extraction Rate Limit Throughput

Thena's standard-tier API enforces a limit of 60 requests per minute, so extracting 5,000 requests with their conversations requires approximately 167 minutes of API time, demanding a multi-hour extraction window or negotiated Enterprise-tier limits.

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 LiveChat and built proven solutions for each one.

High complexity

Conversation Messages

Slack-threaded message content must be flattened, chronologically sorted, and converted from mrkdwn to HTML, with strict ordering enforced by HelpDesk's API or the entire ticket import fails with a 422 error.

Solved
Agent Authorship

Missing or unresolved agentID values cause HelpDesk to silently reassign agent messages to the requester, producing data corruption with no API-level error signal.

Solved
Attachments

Attachments require a 3-step transaction flow with a 24-hour expiry window; failed mid-transaction uploads cannot be recovered and force a full restart, making attachment migration the highest operational risk in the pipeline.

Solved
CSAT / Feedback

Thena's feedback[] CSAT data has no import path into HelpDesk's rating system and will be permanently lost unless manually archived externally before migration.

Solved
Workflows and Routing Rules

Thena's Slack routing rules, AI agent configurations, escalation logic, and internal thread behavior have no import path and must be fully redesigned in LiveChat and HelpDesk from scratch.

Solved

Custom engineering

Tickets / Requests

Core request data fields map to HelpDesk's imported ticket structure, but status and sub-status require custom transformation logic and free-form Thena sub-statuses may not have a clean HelpDesk equivalent.

Handled
Custom Fields

Thena custom fields must be pre-created in HelpDesk via API before ticket import, and HelpDesk restricts field types to four options with strict character limits (120 chars for single-line, 1,000 for multi-line), which may truncate Thena field values.

Handled
Contacts / Requesters

Thena requester identity is tied to Slack user IDs, requiring Slack API resolution to obtain email addresses and display names, and any unresolved users will result in incomplete or anonymous requester records in HelpDesk.

Handled
Accounts / B2B Account Context

Thena's first-class account and customer contact model has no direct equivalent in HelpDesk, so account context must be selectively mirrored into HelpDesk custom fields or retained in an external CRM.

Handled

Clean transfer

Tags

AI-generated Thena tags can be pre-created in HelpDesk via POST /v1/tags and referenced by UUID in the ticket payload, making this a straightforward mapping with low transformation risk.

Clean

What Our Customers Say

Real migration stories

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.”

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.”

See all customer stories →

CUSTOM MIGRATION

Fully customizable engineer-led migration

Tailor your migration from Thena to LiveChat 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 Thena to LiveChat 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 LiveChat, 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 Thena to LiveChat 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 Thena and LiveChat 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 Thena data and LiveChat
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 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 LiveChat 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 Thena to LiveChat. Can't find what you're looking for? Talk to our team.

Can I import Thena data directly into LiveChat?

No. LiveChat handles real-time chat sessions, not historical ticket imports. LiveChat's legacy ticketing was sunset in January 2025. Historical Thena data must be imported into HelpDesk via the POST /v1/importedTickets endpoint.

How do I handle Slack users without email addresses during the migration?

HelpDesk requires an email address for every requester. Query the Slack API (users.info with users:read.email scope) to resolve Slack IDs to emails. For users whose workspaces restrict email visibility or who are deactivated, generate a fallback email like unknown-{slack_user_id}@migration.internal and tag those tickets for manual review.

Can I preserve original timestamps from Thena in HelpDesk?

Yes. HelpDesk's imported tickets API lets you set historical dates on events — the first message's date becomes the ticket creation date. Events must be chronologically ordered and all dates must be in the past. LiveChat chat events, by contrast, use server-generated timestamps that cannot be overridden.

Can I preserve Thena's AI-generated metadata in HelpDesk?

Not natively. HelpDesk has no fields for AI summaries, sentiment, or urgency sources. Store them in HelpDesk custom fields (singleLine: 120 chars, multiLine: 1,000 chars), append them to the ticket body, or discard them.

How long does a Thena to LiveChat migration take?

For 3,000 requests with conversations: roughly 3-4 hours of API runtime. Thena's 60 req/min rate limit is the bottleneck. Add development time for scripting, Slack user resolution, and validation — typically 3-7 days of total engineering effort.

How long does the Thena to LiveChat 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 LiveChat?

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→LiveChat migration.

Contact our team

Ready to start your
LiveChat 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 Thena to LiveChat with precision & ease

Why teams migrate from Thena to LiveChat