Migrate your Mission Control data

Projects are the top-level container in Mission Control. We export project name, description, status, dates, owner, and member list. Sub-project hierarchies are flattened to a flat list with parent-reference during migration.

Tasks carry name, description, status, priority, assignee, due date, and custom fields. We preserve status values as-is and map them to the destination enum. Task ordering within a project is preserved via a sequence index field.

Subtasks nest under tasks with the same field set. Deep nesting beyond three levels is flattened by Mission Control's export, so we reconstruct the hierarchy up to three levels and attach the remainder as flat sibling tasks with a parent_reference field.

Users have name, email, role, and avatar. Teams are groupings of users. We export all user records and team memberships, mapping email addresses to the destination system and flagging any unresolvable accounts.

File attachments are stored with a name, size, mime type, and URL. We preserve the URL reference and download metadata; actual file content transfer depends on whether the source storage is publicly accessible or requires authenticated fetch.

Comments are timestamped, authored entries attached to Tasks or Projects. We export full comment text, author, and timestamp ordering, preserving the thread sequence in the destination system.

Custom fields vary by account. We extract all custom field definitions and values per object, map them to destination custom fields by name match, and flag any without a corresponding destination field for manual post-migration configuration.

Workflow rules define trigger-condition-action sequences. We export the full rule configuration as a JSON document and present it as a setup guide for the destination platform rather than as an importable artefact, since workflow formats are not portable across vendors.

Tags are simple string labels applied to Tasks and Projects. We export the full tag vocabulary and apply tag values to matching destination records. Tags without a destination match are attached as a comma-separated note field.

Mission Control exposes integration configurations for connected third-party tools. We export the list of active integrations and their credentials sanitized (tokens replaced with placeholders) so the customer can reconfigure connections at the destination.

Role-based permissions are exported as a role matrix showing what each role can access. Actual permission enforcement is destination-system-specific and must be reconfigured manually post-migration. We do not transfer permission grants as executable rules.