Migrate your Sqanit data

Sqanit calls these Assets or Digital Twins. Each device carries metadata (model, serial, install date, owner) and a service history. We map Assets 1:1 but flag custom fields added per customer config, as the schema varies between accounts.

Organization records represent the manufacturer or enterprise account. These map cleanly to a standard Company/Account object in most destination CRMs with a simple field-level rename.

Service Tickets are the core transactional object in Sqanit. They carry status, priority, assignee, timestamps, and linked device context. Status and priority values may differ between source and destination systems; we apply a mapping table during migration.

End Users are consumers who scan the QR code on a product. They may have minimal profile data (language preference, device ownership). We migrate End User records and preserve the link to the device, noting that destinations without a consumer-facing layer may need a different object.

Internal service team members assigned to tickets. We map these to Users or Contacts depending on the destination's object model, preserving role and team assignment where those fields exist.

Sqanit tracks device compliance status (inspections, certifications, regulatory records) as a linked object. These are often custom-structured per industry (medical devices, EU Digital Product Passport regulations). We extract and remap them as custom objects or structured fields in the destination.

Every scan, AI-assisted resolution, or ticket update creates an interaction record. These are timestamped, device-linked, and sometimes multilingual. We preserve the full interaction log as a chronological array or activity feed in the destination.

Sqanit supports 524+ languages for self-service content. KB articles and guided workflow text exist per locale. We extract article content and locale tags, then map them to the destination's knowledge base structure.