eDesk — Migration Reference

Role in migrations

• Staff (HD): supported as both (source and target).
• Contact (HD): supported as both (source and target).
• Ticket (HD): supported as both (source and target).

Field-level support migrating FROM eDesk (Ticket)

Field-level support migrating TO eDesk (Ticket)

Field-level support migrating FROM eDesk (Contact)

Field-level support migrating TO eDesk (Contact)

Migration options available for eDesk

• Migrate the newest records first - applies to: source (Ticket)
• Select records for Demo - applies to:  source (Ticket)
• Skip ticket attachments - applies to: source (Ticket)

eDesk — Setup & How-To Guide

For more information: https://help-desk-migration.com/help/edesk-data-migration-checklist/

Limitations

1. Ticket attachments larger than 10MB cannot shift to eDesk.
2. The migration tool can transfer custom fields in a private note using a customized approach.
3. You can import to eDesk only with a free trial or an Enterprise plan.
4. If a ticket has two requesters, all replies will be assigned to the source requester.
5. If a contact is deleted on the Source platform, the Migration Wizard moves its name +example.com to eDesk.
6. Migration Wizard can’t import groups, organizations, inline images, tags, custom fields, macros, triggers, automation, and other settings.
7. By default, you can transfer one workspace/mailbox/inbox in one Full Migration. For some source help desk platforms, you should filter data on the source account and send distinct data batches to different inboxes. So, if you have multiple mailboxes, set up a Full Migration for each.