Migrate from Ivinex to Zoho Desk

Ivinex User accounts (name, email, role, active/inactive status) map to Zoho Desk Agent records. We extract all Ivinex users so owner assignments on Tickets can be remapped to the Zoho Desk agent list. Pre-flight validation confirms that the migration API user has explicit read access to the Users Tab before extraction begins. Inactive Ivinex users cannot have their case assignments migrated to Zoho Desk because Zoho does not accept deactivated agent assignments; these are flagged in the reconciliation report for admin review.

Ivinex Organization records map to Zoho Desk Account. Standard fields (organization name, phone, email, website, address) migrate directly. Organization records optionally link to Ivinex Contacts via LinkRecords; we resolve those links by creating the Account first, then the Contact with the AccountExtId reference populated during the Contact phase.

Ivinex Contact records map to Zoho Desk Contact. Standard fields (first name, last name, email, phone, mobile) migrate cleanly. Ivinex custom fields on the Contact Tab are discovered via GetFields, created as custom fields in the Zoho Desk Contacts module within the relevant department, and then populated during the Contact insert. Any Ivinex Contact without an email address is flagged for manual review because Zoho Desk requires an email for agent-facing Contact records.

Ivinex Ticket records map to Zoho Desk Ticket. The primary work item fields (status, priority, assignee, description) migrate to the corresponding Zoho Desk Ticket fields. We pre-create any Ivinex custom fields on the Ticket Tab as Zoho Desk custom fields scoped to the target department before the Ticket import phase. Ticket status values are mapped to Zoho Desk status values (Open, Pending, On Hold, Closed) during the transform phase.

Ivinex activity records attached to Tickets via GetAllRelatedItems (call logs, emails, notes) map to Zoho Desk Ticket Threads and Comments. Each Ivinex activity type maps to a thread type in Zoho Desk: inbound emails become Reply threads, outbound emails become Note threads, call logs become Note threads with a custom call disposition field. The author of each activity is resolved to the Zoho Desk Agent by email match. CC recipients on Ivinex email activities are flagged for manual migration to a custom field because Zoho Desk does not natively migrate CC user lists.

Ivinex Task Tab records map to Zoho Desk Task records linked to the parent Ticket via the WhatId reference. Due dates, assignees, and completion status migrate directly. Task status is mapped to Zoho Desk Task status values (Not Started, In Progress, Completed, Deferred). Ivinex tasks not linked to a Ticket are flagged as orphan tasks and migrated as standalone Tasks with a flag for manual re-linking.

Ivinex allows unlimited custom fields on every Tab with types including text, number, date, dropdown, checkbox, and user-link. We enumerate all custom fields via GetFields for every Tab before any data pull. Each custom field is created in Zoho Desk under the relevant department and module (Tickets, Contacts, Accounts, Tasks) with a matching field type. Ivinex dropdown options become Zoho Desk picklist values; Ivinex checkbox becomes Zoho Desk checkbox; Ivinex date becomes Zoho Desk date. User-link fields require a separate resolution step to map the Ivinex user reference to the Zoho Desk Agent ID.

Ivinex attachment metadata (file name, URL, size) is extracted during the GetRecords pass, but binary file content requires a separate download step because the API does not inline binary data. We execute parallel downloads in a second pass, validate file integrity via MD5 hash if available, then re-upload to Zoho Desk as ContentDocument records linked to the parent Ticket, Contact, or Account via ContentDocumentLink. Large files (over 25 MB) are flagged for a dedicated post-ETL file transfer because they may exceed Zoho's default attachment size limits per the customer's Zoho Desk edition.

Ivinex Groups control API permissions and record access. We export group membership during scoping so that access controls can be documented for reconstruction in Zoho Desk. Groups do not map 1:1 to Zoho Desk Teams because the permission models differ; we deliver a written access-control mapping document showing which Ivinex Groups correspond to which Zoho Desk Teams and role assignments (Agent, Light Agent, Support Administrator) so the customer's admin can rebuild the security model post-migration.

Ivinex audit trail records (field-level change history) are scoped for filtered export by date range only if the customer requests them. Full change history across all records can be large and does not have a standard Zoho Desk equivalent. If the customer requires audit history, we deliver it as a structured JSON export with record ID and field-change timestamps, stored alongside the migration package for compliance review.

Ivinex automation rules defined in the process automation module do not migrate to Zoho Desk Blueprints because the rule structure, triggers, and actions are platform-specific. We export workflow configuration as structured JSON showing trigger conditions, branch logic, and downstream actions. The customer receives a written workflow inventory document with each workflow's recommended Zoho Desk Blueprint equivalent, and the admin rebuilds them post-migration.

Ivinex Saved Views define which fields and filters are shown per Tab and are user preferences rather than data. We preserve view names and filter criteria in a written handoff document so the customer can rebuild them as Zoho Desk Custom Views and Filters post-migration. Zoho Desk Custom Views are accessible under the Tickets, Contacts, and Accounts modules in Setup.