Re:amaze to Tidio Migration

MIGRATION OVERVIEW

Why teams migrate from Re:amaze to Tidio

The core problem

Migrating from Re:amaze to Tidio requires a full data model translation with no native, end-to-end migration path between the two platforms. Re:amaze structures support around continuous, reopenable Conversations tied to Contacts, Channels, and Brands with 8+ distinct lifecycle states, while Tidio enforces a flatter hierarchy of Contacts, Tickets, and Conversations with only three status values (open, pending, solved). Critical objects such as the Re:amaze knowledge base, staff/operator records, departments, and response templates have no writable API endpoints in Tidio and must be rebuilt manually. Custom work — ranging from API extraction and JSONL transformation to status remapping and contact property flattening — is required for any migration that preserves conversation history and custom field data.

Why this matters for your migration

KEY CHALLENGES

What makes this migration complex

These are the architectural mismatches and technical hurdles specific to a Re:amaze to Tidio migration.

Most Critical

Conversation Status Model Compression

Re:amaze supports 8+ distinct conversation lifecycle states (Open, Responded, Done, Spam, Archived, On Hold, Auto-Done, and AI-related states) that must be compressed into Tidio's three-value model (open, pending, solved), resulting in unavoidable information loss unless source states are preserved in custom fields or tags.

Blocks all downstream imports if mapped wrong

Read-Only Operator and Department APIs

Tidio's Operators and Departments API endpoints are read-only, meaning staff members and department structures cannot be programmatically created during migration and must be manually rebuilt in the Tidio admin interface before ticket assignment can be mapped correctly.

Knowledge Base Has No Import Path

Re:amaze exposes a full CRUD Articles API for its knowledge base, but Tidio provides no equivalent import API or knowledge base feature, requiring all help content to be manually rebuilt or archived externally with permanent loss of URL structure and article metadata.

Contact Identity Flattening

Re:amaze supports multiple Identities per Contact (email, social, phone, etc.), whereas Tidio contacts support a single primary email address, requiring additional identities to be either stored as custom contact properties or discarded entirely.

Timestamp and HTML Fidelity Constraints

Tidio's standard REST API ticket creation endpoints do not reliably preserve original message timestamps or HTML email body content, requiring the use of the JSONL ticket import pathway — which is documented primarily in the context of Zendesk migrations and must be confirmed with Tidio support for general use.

Rate Limit Throttling at Scale

Tidio enforces strict API rate limits of 60 requests per minute on Plus plans and 120 on Premium, making large-volume migrations inherently slow and requiring robust retry logic, backoff strategies, and extended migration windows for datasets exceeding a few thousand records.

MIGRATION RISK ASSESSMENT

Every migration risk, already solved

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

High complexity

Custom Attributes

Re:amaze custom attributes on both Contacts and Conversations must be manually mapped to Tidio's Contact Properties, which support only limited field types (text, email, number, phone, url), and conversation-level custom fields have no direct Tidio equivalent.

Solved
Knowledge Base Articles

Tidio has no knowledge base feature or article import API, meaning all Re:amaze knowledge base content is permanently lost in the destination platform and must be manually rebuilt in an external system or Tidio's help content if available.

Solved
Staff / Operators

Tidio's Operators API is read-only, so agent accounts cannot be created programmatically and all staff must be manually provisioned in Tidio before ticket assignments can be correctly attributed during migration.

Solved
Departments / Channels

Tidio's Departments API is read-only and Re:amaze Channels have no automated creation pathway in Tidio, requiring all routing structures to be manually recreated before tickets can be correctly assigned during import.

Solved
Satisfaction Ratings

Tidio provides no import mechanism for satisfaction or CSAT data, meaning all historical customer satisfaction ratings from Re:amaze are permanently unmigratable and can only be exported for external archival.

Solved

Custom engineering

Conversations / Tickets

Conversation threads can be mapped to Tidio tickets, but status compression from 8+ Re:amaze states to 3 Tidio states causes structural information loss unless source values are preserved in tags or custom fields.

Handled
Messages / Ticket Replies

Message history can be replayed via the JSONL import path with HTML body and timestamp preservation, but using the standard REST API risks losing original timestamps and rich content formatting.

Handled
Response Templates

Re:amaze response templates have no corresponding import API in Tidio and must be manually recreated as canned responses, with the risk of loss proportional to the volume and complexity of the existing template library.

Handled

Clean transfer

Contacts

Contacts migrate cleanly via CSV or API using email as the deduplication key, though secondary identities beyond the primary email must be flattened into custom properties or discarded.

Clean
Tags

Re:amaze conversation tags map directly to Tidio ticket tags with no structural transformation required, making this one of the cleanest entity transfers in the migration.

Clean

What Our Customers Say

Real migration stories

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

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

See all customer stories →

CUSTOM MIGRATION

Fully customizable engineer-led migration

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

Can I migrate conversation history from Re:amaze to Tidio?

Yes, but only via API extraction or JSONL ticket import — not CSV. Re:amaze's CSV export covers contacts only, not conversation threads. You need to extract conversations and messages from Re:amaze's REST API and recreate them as Tidio tickets with replies. For best timestamp and HTML fidelity, use Tidio's JSONL ticket importer rather than the API create/reply endpoints.

What data is lost when migrating from Re:amaze to Tidio?

Knowledge base articles (Tidio has no KB import), response templates, satisfaction ratings, status page data, VoIP/video call history, original message timestamps (unless you use the JSONL importer), and multi-identity contact links (Tidio supports one email and one phone per contact). Agent assignments, departments, and automations must be manually rebuilt.

Does Tidio deduplicate contacts on import?

No. Tidio's POST /contacts endpoint always creates new contacts regardless of whether the email already exists. You must build deduplication logic into your migration pipeline — query existing Tidio contacts first, index by email, and use PATCH to update existing records instead of creating duplicates. Tidio's CSV/TXT contact import, by contrast, can update existing contacts by email.

How do I preserve original timestamps when migrating to Tidio?

Tidio's API create/reply endpoints stamp the import time as the creation time, not the original Re:amaze timestamp. To preserve original dates, use Tidio's JSONL ticket importer, which supports a createdAt field. As a fallback, prepend the original timestamp to the message body.

Do I need Tidio Plus or Premium for an API-based migration?

Yes. Tidio's OpenAPI is available exclusively on Plus and Premium plans. Free and Starter plans do not have API access. Plus allows 60 requests/minute and Premium allows 120 requests/minute. Confirm your plan before investing in API-based migration development.

How long does the Re:amaze to Tidio 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 Re:amaze 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 Re:amaze to Tidio?

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 Re:amaze→Tidio migration.

Contact our team

Ready to start your
Tidio 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 Re:amaze to Tidio with precision & ease

Why teams migrate from Re:amaze to Tidio