Migrate from Sqanit to HubSpot Service Hub

Sqanit's Device/Asset records carry model, serial number, install date, owner metadata, and a full service history. These map to a HubSpot custom object (Asset__c or Device__c) created during schema setup, with custom fields for serialnumber, model, install_date, and owner_contact. The device-to-ticket link preserves by migrating Tickets after Assets and populating the device lookup field. EU Digital Product Passport compliance fields map to custom Asset__c fields per industry requirements. This object is unique to Sqanit and requires custom schema creation in HubSpot before migration.

Sqanit Organization records represent the manufacturer or enterprise account and map cleanly to HubSpot Company. The Organization name becomes Company Name, and the domain or primary contact email becomes a dedupe key. Standard address and industry fields map from Organization address properties where present.

Sqanit Service Tickets are the core transactional object carrying status, priority, assignee, timestamps, and device context. Status and priority values require a value map during migration (Sqanit statuses differ from HubSpot's default New, Open, Pending, Solved, Closed). We create HubSpot ticket pipelines matching Sqanit active stages and configure priority mapping from Sqanit priority levels (Low, Medium, High, Critical) to HubSpot priority (Low, Medium, High, Urgent).

Sqanit End Users are consumers who scan the QR code on a product. They may have minimal profile data (language preference, device ownership links). We migrate End User records to HubSpot Contact with language preference preserved in a custom property. The device-ownership link migrates by resolving the associated Device__c lookup at migration time. End Users who also appear as Organization contacts receive deduplication by email.

Sqanit Technicians are internal service team members assigned to tickets. We map these to HubSpot User if they are active HubSpot seat users, or to Contact if they are external technicians tracked in Sqanit but not provisioned as HubSpot users. Role and team assignment from Sqanit map to HubSpot User role and team fields where those properties exist in the source export.

Sqanit tracks device compliance status (inspections, certifications, regulatory records) as a linked object often custom-structured per industry. These migrate to a HubSpot custom object (Compliance_Record__c) with lookup to the Device__c custom object. For Sqanit configurations where compliance records are stored as unstructured data, we attach them as HubSpot Notes linked to the Device record. Industry-specific fields (medical device inspections, EU DPP fields) require custom schema mapping per account during discovery.

Every scan, AI-assisted resolution, or ticket update in Sqanit creates an interaction record timestamped, device-linked, and sometimes multilingual. We extract the full interaction log as chronological entries. AI triage interactions become HubSpot Task records with a custom interaction_type field; technician resolutions become Task records with status Completed; device scans become Event records with location metadata. The original timestamp preserves on ActivityDate for timeline ordering.

Sqanit supports 524+ languages for self-service content with KB articles and guided workflow text per locale. We extract article content and locale tags, then map them to HubSpot Knowledge Base articles using HubSpot's pre-built Knowledge Base importer. Note that inline images embedded in articles do not migrate per HubSpot's import limitation; we flag these during scoping and the customer replaces them manually post-migration. Knowledge base groups from Sqanit do not transfer to HubSpot groups.

Sqanit tracks product registration records linked to devices and end users. These map to HubSpot Product2 records with a custom registration_date field and lookup to the Device__c custom object. Product registration ownership links to the associated Contact record in HubSpot.

Sqanit's QR code routing configuration (which QR codes trigger which triage flows, self-service paths, or technician assignments) has no direct HubSpot equivalent. We document the QR code routing logic as a written configuration inventory for the customer's admin to implement in HubSpot using help desk routing rules, canned snippets, and conversation automation. This is not migrated as code.

Sqanit's AI-assisted triage rules and guided workflows evaluate device type, symptom description, and user language at the first QR scan. These do not migrate to HubSpot. We deliver a written inventory of active triage rules with their trigger conditions and recommended HubSpot equivalents (Breeze AI Customer Agent on Professional+, or manual routing rules on Starter). The customer's admin rebuilds these in HubSpot post-migration.

Sqanit's modular deployment means each account activates a different combination of Service Management, Asset Management, and CX Management. We document which modules are active, which objects are populated, and which custom fields exist per module configuration as part of the discovery output. This configuration audit serves as the schema scope definition for the HubSpot migration and is handed off as documentation, not as migratable data.