Migrate your Alloy Navigator data

Tickets (Service Requests) are the primary record type with a rich lifecycle spanning open, pending, resolved, and closed states. We export ticket fields, linked activities, and conversation history. Status and priority values are configurable per customer, so we map these against the destination system's schema during import.

Assets include hardware devices, software licenses, and consumables tracked across their full lifecycle from procurement to retirement. We migrate asset records including purchase info, assigned users, and linked contracts. The asset-to-configuration-item relationship is preserved via a reference field.

Configuration Items (CIs) model IT infrastructure components and their interdependencies. We export CI records and their relationship graph. Custom CI types introduced via classification are detected and included, though relationship types require explicit mapping to the destination object model.

KB articles contain formatted text, attachments, and category assignments. We export article body, metadata, and attachments. Category hierarchies may not map 1:1 to destination systems — we flag category name collisions and flatten deep hierarchies on request.

Organizations represent customer or partner entities with hierarchical Location records. We export org details and the full location tree. The location hierarchy depth varies by customer and may need normalization during import into flat-account models.

Contacts are people linked to Organizations, Tickets, and Assets. We export contact fields, email addresses, and organizational associations. Duplicate contact handling requires a pre-migration dedup step when contacts share the same email across organizations.

Work Orders manage scheduled tasks, assignments, and completion tracking separate from reactive tickets. We export work order records, schedules, and assignee mappings. Custom work-order-specific fields are included but may require destination field creation.

Contracts link to Assets and Contacts with renewal dates, terms, and costs. We export contract metadata and linked asset references. Multi-document contracts with binary file attachments require file migration separately from the record export.

Workflows drive business process automation including approval chains, escalations, and Create Actions. We export workflow definitions and configuration parameters. Complex conditional branching and third-party action plugins may require re-authoring in the destination system.

User records include login credentials, team assignments, workload-balancing groups, and role-based permissions. We export user profiles and role mappings. Active versus inactive status must be explicitly set at import to avoid creating orphaned active accounts.

Software licenses track compliance, seat counts, and purchase records attached to Assets. We export license details and compliance metrics. License entitlement calculations are source-system-specific and may need manual reconciliation in the destination.

Locations form a hierarchical tree representing physical sites for Organizations. We export the full location hierarchy including address data and parent-child relationships. Deep trees with more than five levels may need flattening depending on destination schema limits.