Merging two Zendesk accounts - a step-by-step process

7 Comments

  • Anton vh

    What would be the best way to deal with the fact that the ticket ids will be different from the original data? The issue is once you import all your tickets a new ticket id will be auto-assigned so any previous communication links, integrations, or references will be broken. If the 'id' value can be provided one could maybe force the old id where it has not already been used by the destination instance and at least limit the number of changes, or should one add the old id to the new external_id field (or a new "old_id" custom field or tag) to at least make it searchable?

    0
  • Migration Support

    Hey Anton,

    The easiest way is to create a new custom field on your new platform and map it with the ID field from your source platform.

    0
  • Anton vh

    Thanks, what about SLA metrics can they be brought across, and how many tickets can be migrated at a time?

    0
  • Dima Lazarchuk

    Only tickets

    0
  • Dima Lazarchuk

    Zendesk Admin, sure thing!

     

    0
  • Jason Wong

    In Step 5 above where it mentions to turn off triggers, automations and notifications does that mean if migrating from source -> destination that these will be copied across or does one have to recreate all those.  

    I am looking at how to manage and perform best practices on consolidating two instances. I assume that you have create all the forms, fields(custom fields) webhooks and targets on the destination instance before migration can be initiated or is that part of the process that is done during migration.

     

    0
  • Natalia Tomchyshyn

    @Jason Wong, in the concierge migration service, we can manually create triggers, automations and notifications.

    If you need more details, leave your email or schedule a free call and our customer service reps will help you and explain all the options.

    0

Please sign in to leave a comment.

Powered by Zendesk