Migrate from Ivinex to Zendesk

Zendesk Guide must be activated before knowledge base migration

Ivinex does not have a native knowledge base, but teams that manage support articles externally (Google Docs, Confluence) will want to migrate them to Zendesk Guide. However, Guide is a separate product tier that must be explicitly activated in the Zendesk Admin panel before any article migration can begin. FlitStack cannot create Guide sections or articles until the product is provisioned. If your Zendesk plan does not include Guide, the knowledge base migration step must be deferred or scoped separately — this affects the overall timeline and pricing estimate.

Zendesk requires users to exist before tickets can reference them

Ivinex links tasks to contacts without requiring the contact to be 'activated' as a user. Zendesk enforces a hard dependency: a ticket's requester_id must reference an existing Zendesk user. Ivinex contacts without email addresses cannot be created as Zendesk users, which means they cannot appear as ticket requesters. We resolve this by creating a placeholder user record with a generated email for contacts missing addresses, or flagging them for your team to supply an email before migration. This step adds validation overhead and can delay the ticket migration phase if a large percentage of Ivinex contacts lack email addresses.

Custom object relationships require Zendesk's new relationship key model

Ivinex's LinkRecords API creates N:N relationships between any two records (contact-to-task, company-to-company, custom-module-to-contact). Zendesk's custom objects support relationships via a dedicated relationship key field introduced in the newer custom objects experience, but legacy Ivinex custom object relationships that were modeled as multi-linked records may need to be flattened into a single relationship key or stored as a text field of comma-separated record IDs for reference. We surface this in the migration plan before committing data so your admin can decide on the target model.

Zendesk's API rate limits cap large-volume migration speed

Zendesk's Tickets API enforces rate limits that can throttle migration throughput for large Ivinex datasets. The Zendesk API allows approximately 700 requests per minute on most plans, but bulk operations (creating users in batches) have their own limits. Ivinex's own API also has permission-scoped rate limits that affect how quickly we can pull data during the export phase. FlitStack manages a sliding window across both APIs to maximize throughput without triggering 429 errors, but datasets exceeding 100,000 records will see longer migration windows than the raw record count suggests — the API handshaking overhead compounds at scale.

Ivinex email templates cannot be imported as Zendesk macros

Teams using Ivinex's email template feature to store standardized customer communications will need to rebuild those templates as Zendesk macros. The Ivinex template variable syntax (e.g., {{contact.first_name}}) does not match Zendesk's placeholder format ({{ticket.requester.name}}). FlitStack exports the template body text and the list of merge fields used, producing a rebuild checklist your Zendesk admin can use to recreate the templates. This is a manual post-migration step — macro recreation is not included in the data migration scope.