Migrate your Siit data

Requests is the core ticket object in Siit. Each request has a title, description, submitted_from channel (employee_portal, slack, mail, ms_teams), status, priority, assignee_admin_uid, target_uid, SLA dates (first_replied_at, first_completed_at), and tags. We migrate full request histories including archived records, custom_form_inputs, and all SLA tracking data via the REST API.

People records store employee directory data including department, team, office location, legal entity, employment type, and lifecycle stage. Export tabs include directory data and group memberships. We map People records to destination employee or contact objects preserving org structure relationships.

Services represent the IT catalog items employees request. Each service has configuration metadata, category assignments, and can be associated with workflows. We migrate the full services catalog including active/inactive state and service-to-workflow associations.

Application inventory tracks software assets with ownership fields, lifecycle status, and category metadata. We export app inventory records including which employee or equipment each application is assigned to, preserving the ownership relationship.

Equipment records represent physical and virtual devices with lifecycle attributes, ownership details, and key configuration fields. We migrate device inventory records preserving equipment-to-person assignment and lifecycle state (active, decommissioned, etc.).

Workflows in Siit include titles, trigger conditions, categories, and state (Live, Paused, Draft). Usage counts are also exportable. We capture workflow definitions and state at migration time; workflow logic (automated actions) is recreated in the destination platform as closely as the target's capabilities allow.

Communication exports include outbound messages and satisfaction survey responses linked to requests. We extract conversation threads with timestamps and satisfaction ratings, mapping them to the corresponding ticket in the destination system.

Requests support custom_form_inputs as key-value label/value pairs. These are fully exportable but have no fixed schema—they vary per organization. We preserve the full set of custom inputs per request and map them to equivalent custom fields or properties in the destination CRM or helpdesk platform.

Tags are associated with requests via tag_uids arrays. We migrate all tags and their associations, preserving the tagging taxonomy that teams use to categorize and filter requests.

Inboxes route requests to specific teams or queues. We map Inbox assignments to equivalent queue or team structures in the destination platform. The inbox concept may not exist in all destination systems and may need to be represented as a custom field or pipeline stage.

Request records include first_replied_at and first_completed_at timestamps. SLA timers and escalation configurations are exported as part of workflow and request data. We preserve SLA metadata to allow the destination system to calculate compliance rates post-migration.

Admins are the billable seat type in Siit. Non-admin employees can submit requests but do not count toward billing. We migrate Admin user records including role-based access control assignments, but mapping to a destination system requires understanding that the destination may price differently (per user vs per agent).