---
title: "Ada to Re:amaze Migration | ClonePartner"
description: "Ada to Re:amaze: Topics → Article Topics: Ada topics mapped as FAQ article categories. Answers → Articles (FAQ/KB): Bot answers converted to FAQ/KB articles."
source: Ada
target: "Re:amaze"
canonical: "https://clonepartner.com/migrate/ada-to-reamaze"
---

# Ada → Re:amaze migration

Seamless Ada to Re:amaze migration — all records moved with accuracy and care.

## Entity mappings

- **Conversations** (Ada) → **Conversations** (Re:amaze)
- **Messages** (Ada) → **Messages** (Re:amaze)
- **Tags** (Ada) → **Tags** (Re:amaze)
- **Knowledge Articles** (Ada) → **Articles (FAQ/KB)** (Re:amaze)
- **Topics** (Ada) → **Article Topics** (Re:amaze)
- **Answers** (Ada) → **Articles (FAQ/KB)** (Re:amaze)
- **Variables** (Ada) → **Contact Attributes** (Re:amaze)
- **Handoffs** (Ada) → **Conversations** (Re:amaze)
- **Training Data** (Ada) → **Not Available** (Re:amaze)
- **Intents** (Ada) → **Not Available** (Re:amaze)
- **Multilingual Content** (Ada) → **Articles (FAQ/KB)** (Re:amaze)

## What we migrate

### Migration Filter

- **User Selection** — Migrate tickets for specific users or agents
- **Time Range** — Migrate tickets from a specific time period
- **Conversation Type** — Filter by chat, email, or social media conversations
- **Tag-Based Selection** — Migrate tickets with specific tags only

### Data Types

- **Knowledge Base** — Articles, categories, and help center content
- **Tickets & Conversations** — Full conversation history with all metadata
- **Customer Profiles** — Customer information and interaction history
- **Automations & Macros** — Workflows, templates, and automation rules

## Frequently asked questions

### 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_<name> so nothing is lost and they can still be identified and reassigned later.

## Get a fixed-price quote

[Talk to an engineer](https://clonepartner.com/talk-to-us?duration=30&utm_source=xtoy&utm_medium=button&utm_campaign=demo_bookings&utm_content=cta_click&utm_term=demo_button_click) about your Ada → Re:amaze migration.