As the Organization structure has shifted to a more "Parent Account Only" ideology, the migration of Tickets and Users was not a 1:1 direct hand off from the Standalone Zendesk into the Multi-Brand Zendesk. Instead, new logic has been placed in an attempt to move only the parent accounts, as well as a few select child accounts, with the Users and Tickets moving to the closest Organization available (assuming a good match can be found).
The logic for what Organizations were brought over are as follows:
-
All parent accounts present in the PDDS Salesforce.
(Accounts where the GUP ID is equal to the Global ID)Child accounts with separate Apteryx servers under the same Parent Account.
(For example: the AMDPI Corporate Account, and the "Parent" Accounts for each of their separate Apteryx Servers [such as WNYDG, CHR, etcetera])Child accounts with Apteryx Imaging products whose names are unrelated to their parent account.
(For example: the Child Account of Cartersville Smiles 4 U under the Parent Account of Blue Monster Management)Child accounts which the client has requested to be treated as individuals instead of as a conglomerated whole.
(*Good example still pending*)
As the Tickets/Users were migrated, they attempted to connect to the same Organization by matching Gup ID - Global ID. If that didn't work, it attempted to connect to the next closest Organization with a GUP ID - Global ID matching the Parent Account. If that didn't work, or if the originating Organization had faulty information within the GUP ID - Global ID field on the Standalone Zendesk side, then the Ticket and User were migrated instead to the catch-all Organization of "Migration Unallocated" on the Multi-Brand Zendesk side. A guide on handling Users/Tickets found under this catch-all Organization can be found here -> "Migration Unallocated" Ticket/Users