Migrate your Xurrent data

Requests is the primary ticket object in Xurrent. We migrate Requests 1:1 including all standard fields (subject, description, status, priority, requester, assignee, service). Custom properties are mapped via field-level transformation.

Services define the service catalog and scope for Requests. We preserve the service hierarchy and map parent-child relationships. Services control visibility and SLA assignment at migration time.

Xurrent IMR incidents support alert routing, escalation policies, and responder assignments. We map incidents with their linked responders, on-call schedules, and timeline events. Slack/Teams responder additions are preserved as notes on the incident record.

Changes carry risk assessment, approval chains, and implementation plans. The approval workflow configuration must be rebuilt in the target system as workflow rules do not export as data. Change dates and statuses migrate as fields.

Problems link to their related Incidents and store root cause analysis. We preserve the problem-incident linkage graph and any attached knowledge articles.

Knowledge Articles store structured content with categories and visibility settings tied to Services. We migrate articles as content records and flag which services they are visible to on the destination.

SLA policies define response and resolution times tied to priority levels and services. The policy definitions are configuration rather than data — we migrate them as structured records and note which priority-to-SLA mappings apply per service.

Escalation policies define multi-step notification sequences (who gets notified, via which channel, after how long). We export the policy structure and map step-to-user assignments. Step order and timing thresholds are preserved; channel integrations require reconfiguration on the destination.

Playbooks automate incident response steps and link to knowledge articles. Playbook step definitions and conditional logic are configuration records. We export the playbook structure and flag which IMR plan the playbook belongs to for destination mapping.

On-call schedules define rotation order and coverage windows. We export schedule configurations and rotation sequences. The calendar-layer scheduling logic must be mapped against the destination's scheduling model — schedule conflicts or gaps must be reviewed post-migration.

Custom fields on Requests, Services, Incidents, and other objects are supported via Xurrent's extensibility. We map custom field definitions and their values. Custom field types (dropdown, text, date, number) are preserved; the destination must have matching field types configured before import.

File attachments on Requests, Incidents, and Knowledge Articles are migrated as binary blobs with their association to the parent record preserved. Large attachment volume may require chunked migration and destination storage quota review.

Service dependency maps define which services or infrastructure components are related to others for impact analysis. We export dependency graph data and reconstruct the relationship map in the target system as a service map or CI relationship.