Migrate from Front to Thena

MIGRATION OVERVIEW

Why teams migrate from Front to Thena

Migrating from Front to Thena requires a fully custom API-based ETL pipeline, as no native importer or third-party migration tool currently supports this source-to-target combination. Front is architected around a shared-inbox, email-first conversation model where a single conversation can belong to multiple inboxes, while Thena is account-centric and Slack-native, requiring every ticket to be scoped to exactly one team and linked to an account with a valid primary domain. This fundamental data model mismatch means the migration is a schema transformation exercise, not a field-level copy — requiring canonical inbox resolution, HTML-to-Slack body conversion, status remapping, and contact-to-account domain enrichment before any data can be loaded. Custom development effort should be budgeted at one to four weeks depending on conversation volume, data quality, and the proportion of unattributed records.

KEY CHALLENGES

What makes this migration complex

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

Most Critical

No Native Migration Path

Neither Front nor Thena provides a built-in importer for this direction, and no third-party tool currently supports Front as a source and Thena as a target, requiring a fully custom ETL pipeline built against both vendors' REST APIs.

Multi-Inbox Conversation Resolution

Front conversations can belong to multiple inboxes simultaneously, but Thena tickets require exactly one owning team, forcing a canonical-inbox decision rule to be defined and applied programmatically during transformation.

Account Domain Enrichment Required

Thena accounts require a valid primaryDomain field that Front accounts do not mandate, meaning records lacking domain data — typically 10–15% of conversations in instances without CRM integration — must be attributed or enriched before load.

Message Body Format Conversion

Front stores message bodies as HTML email payloads, while Thena is Slack-native and expects plain text or Slack-compatible markdown, requiring a full HTML-to-text or HTML-to-markdown transformation step in the pipeline.

Strict API Rate Limits on Both Sides

Front enforces per-company rate limits as low as 50 requests per minute on the Starter plan, with the search endpoint further capped at 40% of that limit, making full extraction of large datasets a multi-hour or multi-day sequential operation requiring careful backoff logic.

Non-Migratable Configuration Artifacts

Front rules, macros, message templates, SLA policies, AI-generated Topics, Copilot history, shared drafts, and channel connection settings have no import path into Thena and must be manually rebuilt or accepted as lost.

MIGRATION RISK ASSESSMENT

Every migration risk, already solved

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

Migration Challenge ClonePartner Status

High Complexity —

Solved

Accounts

Thena requires a valid name and primaryDomain for every account, but Front accounts can exist without domains, meaning a significant proportion of records require enrichment, domain sourcing, or a manual attribution strategy before the load phase can begin.

Solved

Custom Fields

Custom field type compatibility must be individually verified, as Front types such as boolean have no direct Thena equivalent and require a remapping decision — such as converting to a checkbox or two-option dropdown — that can affect downstream reporting and workflow logic.

Solved

Rules, Workflows, and SLA Policies

Front rules, macros, and SLA policies have no automated migration path into Thena and must be fully manually rebuilt in Thena's workflow builder and SLA management module, representing significant post-migration configuration effort with high risk of operational gaps if incomplete.

Solved

Custom Engineering —

Handled

Conversations / Tickets

Conversations map 1:1 to tickets but require status remapping, canonical inbox resolution for multi-inbox records, and careful preservation of author, timestamp, and inbound/outbound direction across the thread history.

Handled

Messages

The first message must be separated from subsequent messages to populate the ticket description versus public comments correctly, and all HTML email bodies must be converted to a Slack-compatible format without losing content fidelity.

Handled

Attachments

Attachments must be downloaded from Front's CDN and re-uploaded to Thena via the API, introducing binary transfer overhead, potential link rot if Front tokens expire during a long migration window, and additional storage cost considerations.

Handled

Teammates / Agents

Front teammate IDs and Thena user IDs are entirely independent systems, requiring a lookup table to be constructed and validated before migration begins, and any unmatched teammates will leave tickets unassigned.

Handled

Clean Transfer

Internal Comments / Notes

Front's internal comments map directly to Thena's private comments via the is_private flag, making this a straightforward transformation, though each record must be explicitly flagged during load rather than inheriting visibility automatically.

Clean

Contacts

Email serves as the primary key on both platforms, making deduplication reliable, though phone numbers, custom fields, and non-email handles require field-by-field mapping and type verification.

Clean

Fully customizable engineer-led migration

Tailor your migration from Front to Thena 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 Front to Thena 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 Thena, 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 Front to Thena 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 Front and Thena 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 Front data and Thena
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 48 hours of engineer-assigned support post go-live.

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

No two teams configure Front or Thena 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 Front to Thena. Can't find what you're looking for? Talk to our team.

Is there a native migration tool to move from Front to Thena?

No. Neither Front nor Thena provides a built-in migration tool for this path, and no third-party connector currently supports it. You must build a custom ETL pipeline using Front's Core API and Thena's Platform API. Datasets under 500 conversations may work with a manual CSV approach.

What data is lost when migrating from Front to Thena?

Rules, macros, message templates, analytics history, Front Chat widget configuration, AI Topics, Copilot history, shared drafts, collision detection state, and granular routing history do not transfer. These must be rebuilt manually in Thena or accepted as lost.

How long does a Front to Thena migration take?

For a 10K-conversation dataset on default API rate limits, expect 10+ hours of extraction and 30+ hours of loading, plus development and validation time. Total elapsed time is typically 1–2 weeks. Datasets over 25K conversations can take 2–4 weeks or more.

Can I use Front's analytics export for a historical migration?

No. Front's analytics conversation export is capped at 31 days per export and 100,000 rows, and only covers inboxes with ticketing enabled. Use the Core API for primary extraction.

Does Thena's free plan support API-based data import?

No. Thena's API access requires the Standard plan ($79/user/month billed annually) or higher. The Free plan does not include API access, so you cannot run a programmatic migration against it.

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

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 Front→Thena migration.

Contact our team

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

Why teams migrate from Front to Thena