Migrate from Spiceworks Cloud Help Desk to Zendesk

Spiceworks Cloud Ticket records map directly to Zendesk Ticket. We extract ticket ID, summary, description, status, priority, category, creator (requester reference), assignee reference, and timestamps (created_at, updated_at, closed_at) from the JSON export and map them to Zendesk Ticket fields (subject, description, status, priority, tags, requester_id, assignee_id, created_at, updated_at). Spiceworks ticket IDs are preserved in a custom Zendesk field sw_ticket_id__c for audit traceability. Ticket numbering in Zendesk is controlled by the ticket_id_prefix setting; we align this with the customer's existing ticket ID scheme during configuration.

Spiceworks Cloud technician accounts (name, email, role) map to Zendesk User records with role=agent. We resolve each technician by email match against the Zendesk destination. Agents without a matching Zendesk account go to a reconciliation queue for the customer's admin to provision before ticket reassignment runs. Agent groups and role assignments in Zendesk are configured during the setup phase.

Spiceworks Cloud Organizations map to Zendesk Organizations. The export includes org name and primary contact. We create Zendesk Organizations first, then resolve the organization reference on requester records during import. If the customer uses a flat requester model (no organizations in Spiceworks), we assign all requesters to a default Zendesk Organization created at migration start.

Spiceworks Cloud requesters (name, email, phone if present) map to Zendesk end-user records. We deduplicate by email address. Requesters with no email address require manual handoff because Zendesk requires an email for end-user provisioning via API. The requester-to-organization linkage is resolved after the Organizations phase completes.

Spiceworks Cloud Knowledge Base articles (title, body content, category assignment) map to Zendesk Guide articles. We preserve category assignments as Zendesk Section records and map article visibility (internal vs public) to Zendesk article permission settings. HTML body content is sanitized and inserted via Zendesk's Article API. If Spiceworks articles use internal-only visibility, we set the Zendesk article draft status and flag for the customer's admin to review before publishing.

Spiceworks Cloud JSON export does not include attachment files. However, the export provides Spiceworks-hosted attachment URLs for files associated with tickets. We re-download each attachment from the source URL (where still accessible) and re-upload to Zendesk via the Zendesk Attachments API with a 20 MB per-file limit. We resolve the parent ticket ID via the sw_ticket_id__c custom field before attaching. Files exceeding 20 MB or hosted at inaccessible URLs are flagged individually in the migration report for manual handoff.

Spiceworks Cloud tags (flat string list per ticket) map directly to Zendesk Tags. Zendesk's tag model is flat and supports up to 200 tags per ticket. We map each Spiceworks tag string to the equivalent Zendesk tag. Tags used for internal categorization in Spiceworks that should not be visible to end users in Zendesk are noted separately for the customer to suppress in Zendesk's tag display settings.

Spiceworks Cloud custom fields (string, boolean, date, number, select, multi-select) appear in the JSON export but require pre-creation in Zendesk before the import runs. We provide a custom field mapping template during the preparation phase that specifies the Zendesk field type, API name, and dropdown options for each Spiceworks custom field. The Zendesk admin creates these fields before migration begins; we validate their presence and types during the pre-migration audit.

Comment threads and conversation history are explicitly excluded from Spiceworks Cloud JSON export. This is a documented, community-confirmed limitation. We cannot migrate conversation history via the standard export mechanism. During scoping, we flag this gap explicitly, estimate the approximate number of tickets with comments using the JSON export's comment_count field where present, and advise customers to screenshot or manually export critical conversation threads if required for compliance or continuity. Zendesk Comment records will exist only for any comments added post-migration in Zendesk.

Spiceworks Cloud does not expose a reporting API, and historical report data is not available via the JSON export. We do not migrate reports. Customers who need historical Spiceworks reporting data should export via Power BI using Spiceworks' recommended connector before the migration window opens, then import the resulting datasets to a Zendesk-integrated BI tool post-migration.