If we run one last sync after switching our support email over, will it create duplicate tickets?
Yes — if your support email is already connected to the new platform and tickets are flowing in there directly, running a delta sync afterward can pull in the same tickets a second time, since they now exist on both platforms simultaneously. We coordinate sync timing tightly with your email cutover to avoid this, and will flag it if a requested sync falls after your switchover point.
If a ticket needs to be deleted and reimported to fix an issue, does that change its timestamps or history?
No — reimporting a ticket to fix an issue (for example, broken inline images) preserves its original timestamps, ticket history, and other ticket information. Tickets that were modified after the original migration are excluded from any reimport, since overwriting them would lose updates made on the new platform.
Do tags and macros migrate over along with tickets, or only the tickets themselves?
Yes. The sample and full migration include tickets along with their associated tags, so any tags on migrated tickets carry over as part of the ticket data — and all macros are migrated as well.
What happens to tickets owned by agents who don't have an account in the new system?
Tickets owned by agents who don't have a usable account in the destination platform come across unassigned, but are tagged Assigned_to_ so nothing is lost and they can still be identified and reassigned later.
How long does the Ada to Zammad 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 Zammad?
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.
Is migration pricing a flat fee, or does it scale with data volume?
It's a flat fee based on the scope estimate you give us — small variances in actual volume (a bit more or less) don't change the price.
Can we whitelist a single IP instead of opening our network to your migration tool?
Yes — all migration traffic runs through a centralized system using one fixed IP, which your IT team can whitelist instead of opening broader network access.
Will original ownership and authorship on tickets and articles be preserved?
Yes — ownership, author, and created-time metadata are preserved. Where the target doesn't have a native owner field (e.g. tickets becoming list items), this is carried as embedded metadata on the migrated record.
What support do you provide after the migration goes live?
At ClonePartner, we consider ourselves your partners in this journey. We take full accountability for your migration's success. Once your migration goes live, we provide 30 days of comprehensive post-migration support. During this period, we will assist with everything needed to ensure your transition is a complete success.
Will we get a migration report and a ticket-mapping sheet linking old ticket IDs to new ones?
Yes. We provide a comprehensive migration report along with a ticket-mapping sheet that links each old ticket ID to its corresponding new ticket ID. This ensures full traceability, simplifies post-migration verification, and helps your team validate that tickets have been migrated accurately.
After migration, do I contact ClonePartner or the platform's own support if something looks wrong?
ClonePartner is the contact for anything about the migrated data itself. Platform-level behavior — call routing, compose-window UI, and similar configuration — is handled by the destination platform's own support.
If the new system can't natively support an old record type, what are my options?
We handle it case by case: map it to the closest native object, create a custom field or object, fold it into the parent record as text or an internal note, attach it as a file, or keep it in a read-only archive. You see how your chosen approach looks in a sample migration before we run the full set.
Will we get a report showing exactly what migrated versus what didn't?
Yes. You get a final reconciliation report comparing source and target counts for every object.
Superhuman Docs (Coda)
Claude, 
ChatGPT or 
Cursor. Describe the move in plain English; the agent runs it.
Notion
Slab
ConfluenceSoon
Google DocsSoon
