Migrate from Spiceworks Cloud Help Desk to Zoho Desk

Spiceworks Cloud Ticket records map directly to Zoho Desk Ticket. We extract ticket ID, subject, description, status, priority, type, creator, assignee, created timestamp, and closed timestamp from the JSON export. The Zoho Desk Ticket requires a valid assignee_id reference, which we resolve by matching the Spiceworks assignee email against the agent records imported in the Agents phase. Open tickets import as Open; closed tickets import with their original closed timestamp preserved.

Spiceworks Cloud technician accounts (name, email, role) map to Zoho Desk Agents. We extract all distinct assignees referenced on tickets and all administrator accounts, deduplicate by email, and generate the Agents CSV file required by Zoho Desk Zwitch with agentExtId, Last Name, First Name, and Email columns. If a technician email matches an existing Zoho Desk user, the system maps them to the existing account per Zoho's documentation.

Spiceworks Cloud requesters (name, email, phone, organization) map to Zoho Desk Contacts. We extract all distinct creators and requesters from ticket records, deduplicate by email, and generate the Contacts CSV with contactExtId, First Name, Last Name, and Email. If a requester is linked to a Spiceworks Organization, we link the Contact to the corresponding Zoho Desk Account via the accountExtId field.

Spiceworks Cloud Organizations (name, primary contact) map to Zoho Desk Accounts. The JSON export includes org name and primary contact. We generate the Accounts CSV with accountExtId, Account Name, Phone, Email, and Website fields. Accounts import before Contacts so that the accountExtId reference resolves at Contact insert time. Organizations without a name receive a generated account name from the requester email domain.

The Spiceworks Cloud JSON export does not include the full comment thread or internal notes. This is a documented limitation confirmed by Spiceworks community posts from 2022-2024. We cannot migrate conversation history as records. We flag this gap during scoping, document it in the migration checklist, and advise customers to screenshot or manually export critical conversation threads before the migration window opens if continuity of conversation history is required for compliance or customer relationships.

Spiceworks Cloud KB articles (title, body content, category assignment) map to Zoho Desk Knowledge Base articles. We extract article title, body text, and category from the Spiceworks export. Note that Zoho Desk resets KB article dates to the migration date; original creation dates do not transfer. Zoho Desk KB attachments are also excluded from the Zwitch migration per Zoho's documentation, so any Spiceworks KB attachments require separate manual handling.

Spiceworks Cloud custom fields defined in the portal (string, boolean, date, number, select, multi-select) appear in the JSON export. These fields must be pre-created in Zoho Desk before the ticket import runs because the Zoho import does not auto-create custom fields. We provide a custom field mapping template during the preparation phase listing each Spiceworks field name, type, and the corresponding Zoho Desk field to create, including the module (Ticket, Contact, or Account) where it should be provisioned.

Tags applied to Spiceworks Cloud tickets export as a list of string values. We extract all distinct tag values and map them directly to Zoho Desk Tags. Tags are associated with Tickets via the Tag import step after ticket migration completes. If Zoho Desk tags have a character limit that is shorter than the Spiceworks tag name, we truncate to the Zoho maximum.

Spiceworks Cloud Help Desk JSON export does not include attachments. A Spiceworks community post from July 2022 explicitly confirms that the Cloud export will not export any attachment regardless of ticket age. We cannot migrate attachment records as data records. We advise customers to download any critical attachment files from Spiceworks manually before the migration window and re-upload them to Zoho Desk tickets post-migration, or to use Zoho Desk's file upload API to batch-upload after ticket migration.

Spiceworks Cloud ticket categories map to Zoho Desk Departments if the customer uses multi-department configuration. We extract distinct category values from Spiceworks tickets and create corresponding Zoho Desk Departments during the preparation phase. If the Zoho Desk plan is single-department (Standard tier), categories import as a custom Ticket field rather than as separate departments.

Spiceworks Cloud ticket statuses (Open, Pending, Resolved, Closed) map to Zoho Desk Ticket Status values. We extract the distinct status values from the Spiceworks export and map them to the closest Zoho Desk equivalent. If Spiceworks has custom statuses beyond the standard four, we create matching custom status values in Zoho Desk before ticket import. Status transition rules in Zoho Desk are not migrated and must be configured by the admin post-migration.

Spiceworks Cloud ticket priority values (Low, Medium, High, Urgent) map directly to Zoho Desk Ticket Priority. The five-tier Spiceworks model maps cleanly to Zoho Desk's five-level priority scale. Priority values import as part of the Ticket CSV and do not require separate configuration.