Migrate your Motadata ServiceOps data

Requests are Motadata's primary ticket object with full lifecycle stages (Open, Pending, Resolved, Closed) and rich field schemas including Priority, Impact, Category, and custom fields. We map all standard fields 1:1 and handle custom field migration via destination-field creation or property mapping.

Motadata supports auto-discovery of network assets via credentialed scans and manual CI entry. We extract all discovered CI records including CI type, serial number, location, assigned user, and warranty information. Schema differences between source and destination asset models require field-level mapping, particularly around CI relationships and cost fields.

Users are requesters; Technicians are support staff with group memberships and approval authority. Both are exported with role assignments and LDAP sync metadata. We preserve technician-to-group mappings and delegate-level approvals during migration.

Contracts are tied to vendors and supplier records and include custom fields and warranty sync settings. We export contract records with vendor associations, expiry dates, and custom field values. Note that Motadata stores some contract metadata in system fields not accessible via standard export, requiring manual annotation.

SLAs are defined independently and attached to Requests by priority or category. We export SLA definitions including time targets, business hours calendars, and escalation rules. The SLA-to-request associations are preserved by re-applying the same rules in the destination or by setting a migration flag.

KB Articles are created and categorized within ServiceOps and exposed via the self-service portal. We export article titles, content, category assignments, and view counts. Rich-text formatting differences between platforms may require content reconciliation or manual re-publication.

Motadata workflows define conditional automation sequences for Requests, Changes, Approvals, and Assets. Each workflow step contains conditions, actions, and assignee rules. We export workflow definitions as structured JSON and attempt to recreate them in the destination using equivalent automation constructs, though complex multi-step workflows may require post-migration tuning.

Project Management within ServiceOps includes milestones, tasks, and assignments. We export project records and associated task data. The project schema is lightweight; detailed task dependencies and time entries may not map cleanly to all destination PM tools.

Supplier records store vendor contact information, custom fields, and warranty sync settings. We export all supplier records and re-import them into the destination vendor/supplier object, preserving custom field data.

Notification templates drive automated alerts for request updates, SLA breaches, and approvals. We export template content and rule conditions. Since notification rendering varies by destination email system, we map templates to the closest equivalent and flag any conditional logic that cannot be automatically translated.