Ada to Ada Migration — Merge & Consolidate Instances

MIGRATION OVERVIEW

Why teams migrate from Ada to Ada

The core problem

Migrating from one Ada instance to another requires a fully custom, API-driven approach, as Ada provides no native instance-to-instance transfer functionality. The most critical architectural constraint is that conversations and messages can be exported via the Data Export API but cannot be re-imported into a target Ada instance, as no bulk import endpoint exists for historical conversation data. Knowledge articles, end users, custom instructions, and persona configuration can be transferred programmatically, though each object type has distinct API surfaces, rate limits, and payload constraints that must be coordinated carefully. Migrations involving a shift from Ada's scripted bot model to its generative agent model require a near-complete rebuild, as objects like Answers, Blocks, and training questions have no direct equivalents in the generative data model.

Why this matters for your migration

KEY CHALLENGES

What makes this migration complex

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

Most Critical

No Conversation Import Endpoint

Ada exposes no POST endpoint that accepts historical conversation or message records, meaning all conversation data can only be archived externally and never surfaced natively within the target instance.

Blocks all downstream imports if mapped wrong

Data Export API Time Horizon

The Data Export API surfaces only the last 12 months of conversation and message data, requiring teams to accept permanent loss of older records or source them from a separate data warehouse before migration begins.

End User Volume Rate Limits

The End Users API is capped at 60,000 requests per day, meaning large user bases of 500,000 or more profiles require a minimum of nine sequential days to transfer under standard rate limit constraints.

Scripted-to-Generative Model Gap

Scripted bot objects such as Answers, Blocks, and Request Blocks have no automated conversion path to the generative agent equivalents of Knowledge Articles, Actions, and Playbooks, requiring manual reconstruction through the Ada dashboard.

Playbook and Coaching Non-Exportability

Playbook configurations and coaching data are only accessible through the Ada dashboard and are not exposed via any API, making them impossible to migrate programmatically and requiring full manual recreation in the target instance.

Integration Re-Authentication Requirements

While integration configurations can be read from the source instance, connected external platforms require re-authentication and credential re-entry in the target instance, creating dependency on third-party system access during cutover.

MIGRATION RISK ASSESSMENT

Every migration risk, already solved

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

High complexity

Conversations

No import endpoint exists for historical conversations, meaning this data can only be archived to external storage and will never be natively accessible to agents or AI responses within the target Ada instance.

Solved
Messages

Like conversations, individual message records are exportable via the Data Export API but cannot be loaded into the target instance, and the 12-month export window creates a hard ceiling on historical data availability.

Solved
Variables

The Variables API is read-only, meaning metavariable definitions including keys, types, and display names cannot be imported programmatically and must be manually recreated in the target instance before dependent end user or conversation data is loaded.

Solved
Playbooks and Coaching

Playbook and coaching configurations have no API export or import surface and are only accessible via the dashboard, requiring complete manual reconstruction with no automated migration path available.

Solved

Custom engineering

End Users

End users can be created and updated via API, but the 60,000 requests-per-day rate limit introduces significant timing risk for large user bases and requires careful scheduling relative to go-live deadlines.

Handled
Glossary

The glossary supports CSV export and import, but the import operation performs a full replacement of the existing glossary rather than a merge, creating a risk of overwriting any content already configured in the target instance if the import is not timed carefully.

Handled
Integrations and Webhooks

Integration and webhook configurations are API-readable and importable in terms of structure, but connected platforms require re-authentication in the target instance, introducing operational dependency on third-party credential availability during cutover.

Handled

Clean transfer

Knowledge Articles

The Knowledge API supports bulk upsert with full read/write coverage for articles, sources, and tags, making this the cleanest and most reliable migration path in Ada's ecosystem, subject to a 50,000-article-per-instance default limit.

Clean
Custom Instructions

Custom instructions are fully accessible via the Custom Instructions API with both read and write support, making them straightforward to extract from the source and load into the target instance.

Clean
Persona

Persona configuration is readable and writable via the Persona API, allowing bot personality and tone settings to be transferred programmatically with minimal transformation required.

Clean

What Our Customers Say

Real migration stories

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

Direct Review

“Fantastic at both guiding us through the process and helping us fix things as they come up and dial them in.”

See all customer stories →

CUSTOM MIGRATION

Fully customizable engineer-led migration

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

Can you migrate conversation history between Ada instances?

No. Ada's Conversations API creates new live conversations — it does not accept historical imports. Conversation data can be exported via the Data Export API (last 12 months only) and archived to an external data warehouse, but it cannot be loaded into a new Ada instance.

What are Ada's API rate limits during migration?

The Data Export API allows 10 requests per second per endpoint, with a maximum of 10,000 records per page, a 60-day date range per query, and access to only the last 12 months of data. The End Users and Conversations APIs have a limit of 60,000 requests per day. The Knowledge API allows 60,000 requests per day with a 10MB max payload and 50,000 article cap per instance.

How do you migrate an Ada knowledge base to another Ada instance?

Use the Knowledge API to export sources, articles, and tags from the source instance, then bulk upsert them into the target via POST /api/v2/knowledge/bulk/articles/. The upsert is idempotent — running it twice updates existing articles rather than creating duplicates. Wait for indexing to complete (typically under 5 minutes) before testing bot responses.

What happens to Ada end users created via API without a conversation?

End users created through the API that are not associated with a conversation within 24 hours are automatically deleted. You must time end-user creation close to your go-live moment or accept that users will be recreated as they interact with the new bot.

How long does an Ada-to-Ada migration take?

A knowledge-only migration can complete in hours. A full migration including end users, configuration, conversation archival, and validation typically takes 3–7 days depending on data volume and the number of playbooks that need manual recreation. API rate limits are the primary throughput constraint.

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

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

Contact our team

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

Merge & Consolidate Two Ada Instances with zero downtime

Why teams migrate from Ada to Ada