Migrate from Spiceworks Cloud Help Desk to HubSpot Service Hub

Spiceworks Tickets map to HubSpot Tickets with ticket ID preserved as hs_ticket_id for reference. HubSpot Tickets use a pipeline and stage model that Spiceworks does not have natively, so we create a default Ticket Pipeline in HubSpot with stages (New, Open, Pending, Solved, Closed) mapped from Spiceworks status values (New, Open, Waiting on Customer, Resolved). The Spiceworks priority field (Low, Medium, High, Urgent) maps to HubSpot Priority. Summary becomes Ticket Subject; description maps to the initial Ticket conversation entry.

Spiceworks Organizations map to HubSpot Companies. The Organization name maps to Company Name, and the primary contact email maps to the Company domain field. We deduplicate by domain during import and merge Organizations with identical domains. Any Organization without a name is assigned a placeholder derived from the requester's email domain.

Spiceworks Requesters (end users who submit tickets) map to HubSpot Contacts. Email address is the primary dedupe key. We resolve the Contact's associated Company by matching the requester's email domain against the migrated Organization domain list. Requesters without email addresses are flagged for manual review because HubSpot Contacts require an email for the portal access and notification features.

Spiceworks technician accounts (Users) map to HubSpot Users. We match by email address and create a mapping table of Spiceworks technician ID to HubSpot User ID for ticket reassignment. Any Spiceworks technician without a matching HubSpot User email is placed in a reconciliation queue for the customer's admin to provision accounts before migration.

Spiceworks custom ticket fields map to HubSpot Ticket Custom Properties. The destination custom property schema must be created in HubSpot before migration begins, per the Spiceworks Cloud JSON import requirement that field schemas be pre-matched. We provide a field-schema checklist in the preparation phase listing each Spiceworks custom field name, type (string, boolean, date, number, select, multi-select), and the corresponding HubSpot custom property to create.

Spiceworks Cloud Knowledge Base articles with title, body, and category assignment map to HubSpot Knowledge Base articles. Category hierarchy from Spiceworks maps to HubSpot article folders. Article status (Published, Draft) migrates as-is. We preserve the author name as a custom attribute on the HubSpot article. The Knowledge Base portal URL in HubSpot replaces the Spiceworks KB portal after migration.

Spiceworks ticket tags export as a string array in the JSON. We map these directly to HubSpot Ticket Tags. If HubSpot is on a tier that does not support tagging, tags are converted to a label field in the ticket subject line or stored in a custom text property as a comma-separated value for filtering in reports.

The Spiceworks Cloud JSON export does not include attachment binaries, only the attachment URL reference. We capture every attachment URL from the export JSON, re-download each file from Spiceworks-hosted storage, and attach them to the corresponding HubSpot Ticket conversation entry by timestamp. Attachments exceeding 20 MB are flagged individually because HubSpot's file attachment limit is 20 MB per file. The built-in Spiceworks Cloud to Cloud attachment migration works differently and does not apply when the destination is third-party.

The Spiceworks Cloud JSON export does not include the full comment thread or internal notes history from the Cloud platform, per confirmed Spiceworks Community moderator guidance. We cannot migrate comment history directly. We flag this gap explicitly in the migration checklist and advise customers to screenshot or manually export critical conversation threads for compliance or continuity. Internal notes and public comments are listed as included in the export in some community posts, but empirical testing shows attachment binaries and full thread context are absent from the Cloud export output.

Spiceworks Cloud does not expose a reporting API. Historical report data cannot be migrated programmatically. Customers who need historical Spiceworks report data should export via the built-in report builder before migration, as Spiceworks itself recommends Power BI for analytics. We do not migrate report definitions or historical reporting data. We deliver a written map of the existing Spiceworks report structure for the customer to recreate in HubSpot's reporting module.

Spiceworks Cloud has minimal ticket automation (basic routing and status rules) with no visual workflow builder. HubSpot Service Automation provides a full visual automation builder with triggers, conditions, and actions. We do not migrate automation rules as code. We deliver a written inventory of every active Spiceworks ticket rule with its trigger conditions, assigned technician or group, and SLA settings, along with a recommended HubSpot Service Automation rebuild approach for the customer's admin to implement post-migration.

Spiceworks uses a Ticket Category field (IT, HR, Facilities, etc.) for routing. HubSpot uses a Ticket Pipeline model instead. We create a HubSpot Ticket Pipeline with pipeline stages as described in the Ticket mapping, and we optionally use HubSpot's custom property field to preserve the original Spiceworks Category value as a read-only label for reference after migration.