Migrate your Myndbend Process Manager data

Parent tickets are standard Zendesk tickets with Myndbend metadata attached. We read all native ticket fields plus Myndbend custom properties (approval status, required approvers) and preserve them 1:1 at migration time.

Child tickets are separate Zendesk tickets linked to a parent via Myndbend's internal reference. We preserve the parent-child linkage and enforce Myndbend's 'child must be solved before parent' blocking logic by replicating it in the target system using workflow rules or ticket dependencies.

Approver assignments live as Myndbend metadata on each ticket, referencing Zendesk user IDs or end-user emails. We read all approver records per ticket and recreate them in the destination as native user assignments or custom multi-user fields.

Approval Groups are named collections of approvers managed within Myndbend's admin settings. We extract group membership and replicate as static user lists or group objects in the target system; any dynamic or condition-based group membership may need manual verification post-migration.

Approval Flows is an early-access feature that defines multi-step sequential approval chains. Flows store revision history as of v4.21. We map the current active flow state and approval chain sequence, but beta endpoints may not expose full audit trail for migration.

Templates define default values and Advanced Properties (custom field settings via JSON) applied when child tickets are created from a parent. We extract the JSON schema for Advanced Properties and map each field ID and mode to corresponding fields in the destination, noting any destination field IDs that differ from Zendesk IDs.

Myndbend allows setting custom field values via JSON using exact IDs, parent_copy modes, or parent_placeholder substitution. We parse the JSON structure per ticket template and map each field ID to its destination equivalent, flagging any unmapped field IDs that require manual field creation before migration.

Myndbend exposes webhook-based actions (add-approvers-by-id, add-approvers-by-email, add-approval-group, execute-approval-flow, etc.) that automate approver assignment via Zendesk triggers. We read all configured trigger messages and attempt to reconstruct equivalent automation logic in the target system, though custom JSON payload structures may need reauthoring.

Myndbend generates branded approval request emails and reminder schedules that are sent from Myndbend infrastructure, not stored as records. These do not migrate — approvers must re-register or be re-invited in the target system.

Ticket Export (beta) allows users to generate on-demand CSV exports filtered by parameters. These are ephemeral export configurations, not persistent workflow data, and have no migration value.