Migrate from Motadata ServiceOps to Zoho Desk

Motadata Requests map directly to Zoho Desk Tickets with status translation: Motadata Open maps to Open, Pending maps to On Hold, Resolved maps to Solved, and Closed maps to Closed. Priority (Low, Medium, High, Critical), Category, and custom fields defined on Requests migrate to Zoho Desk custom fields scoped to the target Department. We resolve the Department reference by matching Motadata's category or request type to the Zoho Desk department structure configured before migration. Attachments migrate as Zoho Desk file attachments linked to the Ticket record.

Motadata Request conversation threads, internal notes, and public comments map to Zoho Desk Ticket Comments with is_public flagged to distinguish internal from customer-facing. The comment author maps to the Zoho Desk Agent record by email match. We preserve the original Motadata comment timestamp as the comment creation date. Rich-text formatting differences between Motadata's editor and Zoho Desk's editor are handled through HTML normalization during the transform phase.

Motadata auto-discovered and manually entered CI records (CI type, serial number, location, assigned user, warranty expiry, and vendor) map to the Zoho Desk Asset module in Professional and above editions. In Zoho Desk Standard or Free editions where the Asset module is unavailable, we map CI records into a custom object with fields mirroring the Asset schema. We validate the destination edition before migration and communicate the Asset routing decision during scoping. Discovery agent timeout gaps identified in pre-migration validation scans are supplemented with manual CI exports to ensure coverage.

Motadata end-users who submit service requests map to Zoho Desk Contacts. The user's email address is the primary key for deduplication. We preserve user-specific custom fields and any group memberships that reflect organizational structure as Zoho Desk Contact custom fields. LDAP sync metadata from Motadata is retained as a reference note for the customer's admin to reconfigure Zoho Desk directory sync post-migration.

Motadata Technicians with group memberships and approval authority map to Zoho Desk Agents. The technician's email is the dedupe key; we match against Zoho Desk Agents by email before inserting. Motadata group-to-technician mappings map to Zoho Desk Team membership if Teams are pre-created by the customer's admin. Technicians without an email in Motadata are flagged during extraction for manual Zoho Desk agent provisioning before the migration phase begins.

Motadata Contracts with vendor associations, warranty metadata, expiry dates, and custom fields map to Zoho Desk in two ways: vendor-linked Contracts attach as Organization-level custom fields on the Zoho Desk Organization record; standalone Contracts with no vendor link are stored as a Zoho Desk custom object or as custom fields on the relevant Asset record. We resolve the Organization reference by matching the Motadata supplier/vendor name to a Zoho Desk Organization created during the reference data migration phase.

Motadata SLA definitions (time targets by priority or category, business hours calendars, and escalation rules) map to Zoho Desk SLA Policies with first response time and resolution time targets translated from Motadata's SLA configuration. The SLA-to-Request attachment is preserved during migration so that the correct SLA applies to each Zoho Desk Ticket based on the priority or category inherited from the Motadata Request. Business hours calendars are recreated in Zoho Desk Schedule within the SLA Policy.

Motadata Supplier records (vendor contact information, custom fields, and warranty sync settings) map to Zoho Desk Organizations. The Organization type field is set to Vendor to distinguish supplier Organizations from customer Organizations. Custom fields defined on Motadata Suppliers migrate as Zoho Desk Organization custom fields scoped to the Organization layout.

Motadata KB Articles with titles, content, category assignments, and view counts migrate to Zoho Desk Knowledge Base Articles. Rich-text formatting differences between Motadata's article editor and Zoho Desk's article editor are normalized during the transform phase; embedded images are extracted and re-hosted as Zoho Desk Media Library assets with URLs updated in the article body. Articles without a category in Motadata are assigned to a default Zoho Desk category for the customer's admin to reorganize post-migration. KB Article status (Published, Draft) is preserved.

Motadata workflow automation rules with conditional steps, approval sequences, and assignee rules map to a written Blueprint documentation deliverable, not executable code. We export every workflow definition including trigger conditions, step sequence, branch logic, and action types, and we recommend a Zoho Desk Blueprint equivalent for each workflow requiring rebuild. Workflow steps referencing Motadata-specific form fields map to those fields' Zoho Desk equivalents if the field migration succeeded; steps referencing unmapped fields are flagged for manual remediation.

Motadata Project records with milestones, tasks, and assignments map to Zoho Desk Tasks organized by project name as a grouping field. Milestones become parent Tasks with subtasks for individual assignments. The project schema in Motadata is lightweight, so detailed task dependencies and Gantt configurations are not present in the export; we document the dependency structure from Motadata as a reference for the admin to rebuild in Zoho Desk Tasks or Zoho Projects if that module is active.

Motadata automated notification templates for request updates, SLA breaches, and approvals migrate as Zoho Desk Email Templates with template content and placeholder variables mapped to Zoho Desk's ticket field placeholders. We flag template rules that reference Motadata-specific fields or actions not available in Zoho Desk (such as patch-triggered notifications) for manual template rebuild in Zoho Desk's Template Editor. Email notification rules attached to specific Request categories map to Zoho Desk's Rules-based email configurations.

Motadata User Groups with member assignments map to Zoho Desk Teams. We export group memberships from Motadata and resolve each member against the Zoho Desk Agent table by email. If a Team does not pre-exist in Zoho Desk, we create it during migration and add the resolved Agents. Team Assignment must be enabled in Zoho Desk Setup before agents can be assigned to Tickets by Team; we flag this prerequisite during the destination configuration phase.

Motadata Change Management records are not a native Zoho Desk object. We map Change records to Zoho Desk Tickets with a custom field changetype__c (Normal, Standard, Emergency) and a custom field changeadvisoryboard__c for CAB approval notes. If the customer uses Zoho Desk Blueprint to model change processes, we document the Motadata Change workflow in the Blueprint deliverable alongside the general Workflow inventory. The mapping approach is confirmed during scoping based on whether the customer wants Change records to appear as Tickets or as a separate process reference.