Migrate from Service Creatio to Zoho Desk

Service Creatio Cases map directly to Zoho Desk Tickets with full field fidelity preserved including case number, subject, description, status, priority, category, and custom columns. We map the Creatio case owner (from the UsrAssignedAgent lookup) to the Zoho Desk Agent by email resolution. SLA timers migrate as Zoho Desk SLA configurations scoped to the relevant department. Case history records (status transitions, timestamped events) migrate as Ticket Activity records. The migration sequence requires Accounts and Contacts to load first so that the ticket-to-contact lookup is satisfied at insert time.

Creatio Account records map to Zoho Desk Account. The account name, address, phone, website, industry, and custom fields migrate directly. We use the Account name as the dedupe key during ingestion. Account hierarchy from Creatio is preserved as parent-account lookup relationships in Zoho Desk where supported. Accounts must import before Cases so that the ticket-account linkage does not fail at insert time.

Creatio Contact records map to Zoho Desk Contact with full name, email, phone, mobile, address, and custom properties preserved. The link between a ticket and its primary Contact record migrates as the ticket's primary contact association. We resolve the contact-account linkage via the AccountExtId field to maintain the Contact-to-Account relationship in Zoho Desk. Inactive Creatio contacts are preserved as historical records with no reassignment.

KB articles migrate with title, body content, category structure, and publication status preserved. Article-to-category assignments map to Zoho Desk's help center category hierarchy. Articles referenced in Case resolution flows are re-linked to the migrated ticket in Zoho Desk at migration time. We flag that internal article links (URLs pointing to other KB articles) will not update automatically after migration because Zoho Desk assigns new article IDs; we provide a cross-reference list of old and new article IDs for the customer's admin to update post-migration.

Creatio Activities (calls, emails, tasks, notes) attach to Cases as child records. We reconstruct the activity timeline as Zoho Desk Ticket Threads and Comments. Each thread is ordered chronologically by the original activity timestamp. Email body content migrates as comments; call metadata (duration, disposition) migrates to custom comment fields. We exclude rich-text columns in the initial export pass to avoid triggering the OData RAM ceiling, fetching them in a secondary targeted query.

Creatio SLA rules define response and resolution time commitments per case category with specific time-bound condition logic. We perform a configuration inventory of all SLA policies and translate them to Zoho Desk SLA policies scoped to the target department. Response-time and resolution-time triggers map from Creatio conditions to Zoho Desk first-response and resolution-time rules. SLA policies require manual alignment of trigger conditions because the condition logic models differ between platforms.

Creatio Queues group cases for team or individual assignment. We export queue membership and routing rules, then map them to Zoho Desk Departments (top-level grouping) and Teams (agent-level grouping within a department). Queue-to-user assignment mappings require review because destination team structures often differ from Creatio queue structures; we provide a written mapping document for the customer's admin to confirm before migration.

Custom objects created in Creatio Studio via the Object type schema require explicit schema discovery before migration. We enumerate all Object schemas during the technical audit, extract column definitions, identify lookup relationships, and translate each to Zoho Desk custom fields on the appropriate module (Case, Contact, or Account). Custom object naming conventions are preserved in the custom field label and API name. We do not create standalone custom object records in Zoho Desk since Zoho Desk does not support a standalone custom object type; we map these as related custom fields on the standard module with the strongest semantic fit.

Standard objects like Cases, Contacts, and Accounts can have custom fields added via Creatio's UI designer. We identify all custom fields during discovery and map them to Zoho Desk custom fields on the equivalent module. Field type mapping requires translation: Creatio lookup fields may become dropdown or lookup fields in Zoho Desk depending on the referenced object. We flag any field type that does not have a direct Zoho Desk equivalent during the scoping phase.

File attachments stored in Creatio's File-type schemas (e.g. ContactFile, CaseFile) migrate to Zoho Desk ticket attachments. We extract file binary data from Creatio separately from the main OData export to avoid triggering the 512 MB RAM ceiling. Large attachment sets are chunked by file count and processed in batches. Note that Zoho Desk's assisted migration tool (Zwitch) does not migrate attachments; our API-led approach handles them directly. Attachment-to-record linkage (which attachment belongs to which ticket) is preserved via the record's external ID.

Creatio Users serve as case owners, activity assignees, and queue members. We map Creatio users to Zoho Desk agents by email lookup. Inactive users are preserved as historical owners rather than reassigned, keeping the audit trail intact. Active users must have a Zoho Desk agent profile provisioned before the Case import phase begins because OwnerId references are validated at insert time. We provide a pre-migration agent provisioning checklist.

Creatio Tags are label objects applied to cases and contacts for classification. We export tag names and their associations to the tagged records. Zoho Desk uses a tag model on tickets; we map Creatio tag labels to Zoho Desk tag names and validate the tag count against Zoho Desk's tag limits per ticket. The customer reviews tag strategy during scoping to confirm whether tags are used for agent categorization, ticket routing, or reporting segmentation.