Migrate from Comidor to Jira

Comidor Issues map directly to Jira Issues (Epics, Stories, Tasks, Subtasks, or Bugs depending on the mapping rule we agree on during scoping). Each Comidor status value maps to a Jira status via a status-mapping table that accounts for status name collisions across different Comidor workflow configurations. The Jira workflow scheme and issue type screen scheme are configured in the destination org before any issue records are created so that incoming records land in the correct state on the correct screen.

Comidor file attachments (binary files and associated metadata) are extracted as separate files with a reference to their parent Issue. During Jira import, each file is uploaded via the Jira REST API and attached to the resolved parent Issue. Jira enforces a 32 MB per-file attachment limit for Cloud instances; we flag any Comidor file exceeding this threshold for the customer's admin to review before migration.

Comidor Contact records (standard fields plus any attached Custom User Fields) map to Jira User accounts resolved by email address match. Comidor Contact is a person record; in Jira, the person record is a User, and the Issue holds the person as Reporter, Assignee, or a custom User-type field. We resolve the User reference at migration time and flag any Comidor Contact whose email has no matching Jira User.

Comidor Account records (organizational entities) map to Jira Components within a Project, or to separate Jira Projects if the Comidor Accounts represent distinct organizational boundaries. The customer chooses the strategy during scoping. Comidor's many-to-many Contact-to-Account relationship is preserved as the Component-to-User membership or as a multi-select custom field depending on the chosen strategy.

Comidor globally scoped Custom User Fields must be extracted as field definitions before any record data. We map Comidor field data types (text, number, date, select, multi-select) to equivalent Jira custom field types (Text Field, Number Field, Date Picker, Single Select, Multi Select). Global Comidor fields that are referenced in multiple Issues are pre-created as Jira project-level custom fields before the first issue record is imported. Any Comidor field whose type cannot be represented in Jira (for example, a complex conditional lookup) is flagged for manual remediation.

Comidor Knowledge Base articles have no native equivalent in Jira Software Cloud. We export articles as structured text records with category assignments. If the customer holds a Confluence license, we deliver a migration package (CSV with article content and hierarchy) that maps to Confluence Pages in a designated Space. If Confluence is not available, articles are flagged as requiring rebuild as project-level documentation inside Jira or as an external Confluence instance.

Comidor Apps created in App Designer are custom-built no-code or low-code applications. We export app configurations as structured definition packages. These packages cannot be imported into Jira as functional applications because Comidor App Designer has no Jira equivalent. We deliver the exported definition as a written configuration inventory so the customer's admin understands what each app did and can rebuild equivalent functionality using Jira's project configuration, issue types, and screens.

Comidor BPMN 2.0 workflow definitions are extracted as portable configuration packages. These define process sequences, conditions, and automated task assignments in BPMN format, which Jira does not natively consume. We deliver the full workflow definition as a written inventory document that includes the BPMN diagram reference, each task's assignee rule, conditional branching logic, and a recommendation for the equivalent Jira Workflow to be built by the customer's admin. Jira Workflows use a different model (status transitions with conditions, validators, and post-functions) and must be rebuilt.

Comidor User Forms are data-entry interfaces that embed Custom User Fields. We export form definitions as structured schemas listing each field, its type, and its show/hide conditional logic. Jira issue type screens perform a similar role, associating a screen (field layout) with each issue type within a project. We map the form field order to the Jira screen field layout, flagging any conditional logic that requires a Jira behaviour or an add-on to replicate.

Comidor discussion board posts map to Jira Issue Comments on the parent Issue. Thread structure is flattened because Jira comments do not support nested reply chains. We preserve the author, timestamp, and full comment body. Any @mentions in Comidor are mapped to Jira account mentions if the target user exists in Jira; unresolved mentions are flagged for the customer's admin to re-tag post-migration.

Comidor User accounts (defining permissions, roles, and organizational placement) map to Jira User records resolved by email address. We extract all distinct Comidor Users and cross-reference them against the destination Jira site's user list. Any Comidor User without a corresponding Jira account is placed in a provisioning queue for the customer's admin to create before record migration begins.

Comidor Teams are groups of Users used in workflow assignments and process routing. We map Teams to Jira Groups or Project Roles depending on whether the team's function is project-level or cross-project. Jira Groups grant permissions and are used in notification schemes; Project Roles scope access within a single project. The mapping choice is made during scoping based on how Comidor Teams are used in workflow definitions.

Process Scheduling in Comidor defines automated recurring execution of Workflows or Issue creation. This is an execution configuration rather than a data record. We do not migrate Process Scheduling as there is no equivalent in Jira Software Cloud. The recurring Issue-creation patterns are documented in the Workflow inventory as a note for the admin: Jira's automation rules or a third-party scheduling app must be evaluated as the replacement mechanism for recurring issue generation.