---
title: "Zendesk to Re:amaze Migration | ClonePartner"
description: "Zendesk to Re:amaze: Help Center Sections → Article Topics: Sections map loosely to topics; hierarchy may be flattened. Engineer-led, zero downtime."
source: Zendesk
target: "Re:amaze"
canonical: "https://clonepartner.com/migrate/zendesk-to-reamaze"
---

# Zendesk → Re:amaze migration

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

## Entity mappings

- **Tickets** (Zendesk) → **Conversations** (Re:amaze)
- **Ticket Comments** (Zendesk) → **Messages** (Re:amaze)
- **Ticket Attachments** (Zendesk) → **Conversation Attachments** (Re:amaze)
- **Users** (Zendesk) → **Contacts** (Re:amaze)
- **Tags** (Zendesk) → **Tags** (Re:amaze)
- **Help Center Articles** (Zendesk) → **Articles (FAQ/KB)** (Re:amaze)
- **Help Center Sections** (Zendesk) → **Article Topics** (Re:amaze)
- **Help Center Categories** (Zendesk) → **Article Topics** (Re:amaze)
- **User Fields** (Zendesk) → **Contact Attributes** (Re:amaze)
- **Organizations** (Zendesk) → **Not Available** (Re:amaze)
- **Macros** (Zendesk) → **Not Available** (Re:amaze)
- **Ticket Fields** (Zendesk) → **Not Available** (Re:amaze)
- **SLA Policies** (Zendesk) → **Not Available** (Re:amaze)
- **Triggers** (Zendesk) → **Not Available** (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

### Will inline images and signatures in migrated tickets break once I shut off my old helpdesk?

Ticket file attachments are rehosted on the destination platform during migration, but inline images embedded directly in email bodies (including signatures) are migrated as-is and can keep being served from your old, source instance. Once that source instance is deactivated, those inline images can appear broken. If this matters to you, we can identify affected tickets and reimport them with images rehosted on the destination before you shut the source down.

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