Migrate from Comidor to Asana

Comidor Issues (entities representing courses of action assignable to individuals, teams, or groups) map to Asana Tasks. We extract Issue fields including title, description, status, priority, assignee, due date, and any attached Custom User Fields. Comidor Issue-to-File attachments map to Asana task attachments. Sub-Issue hierarchies map to Asana subtasks. Comidor's many-to-many linking to Accounts, Contacts, and Files is resolved through Asana's task-to-project membership and the Tasks custom field for cross-reference tracking.

Comidor Custom User Fields are globally defined and referenced across Apps, User Forms, and Workflows. We extract the field definitions first — including field name, data type, validation rules, and picklist options — before any record migration. Each field definition is reviewed for an Asana equivalent: text fields become Asana text custom fields, picklists become Asana enum custom fields, number fields become Asana number custom fields. Fields that cannot map directly are flagged in the handoff document. Because Comidor fields are globally scoped, a single field definition can appear across multiple Apps; we document the cross-reference count so the admin knows which projects will be affected when a field is edited in Asana.

Comidor Apps are custom-built no-code/low-code applications containing forms, fields, and embedded workflows. Each App maps to an Asana Project, and App-level sections or modules map to Asana Sections within the project. If an App spans multiple business domains, we split it into multiple Asana Projects and document the decomposition in the handoff. Comidor's App Designer configurations (form layouts, field embedding) have no direct Asana equivalent and are documented as rebuild requirements for the admin.

Comidor files and documents (stored as attachments or standalone content management assets) migrate as Asana task attachments. We extract binary files with their metadata separately. Asana's API limits attachment size to 100MB per file; any Comidor file exceeding this threshold is flagged for manual download and re-upload. Storage tier restrictions on Comidor source also affect what can be extracted; we audit the active Comidor storage tier during scoping.

Comidor User Forms are data-entry interfaces embedding Custom User Fields and used inside Workflows. We export form definitions as structured schemas including field order, label text, and conditional show/hide logic. In Asana, forms are available on Starter and above and support custom field connections. Conditional logic within Comidor forms does not migrate automatically; we document the conditional rules so the admin can rebuild equivalent logic in Asana Forms or as a pre-migration workflow step.

Comidor BPMN 2.0 Workflows define business process sequences, conditions, and automated task assignments. We extract the full workflow configuration as a portable BPMN definition package. Automated task assignments, routing conditions, and BPMN gate logic do not have a direct Asana equivalent. We deliver the BPMN package and a written workflow inventory listing every active Workflow with its trigger, conditions, actions, and recommended Asana Rules or project structure equivalent. The admin rebuilds the automation logic in Asana.

Comidor Knowledge Base articles with category assignments migrate as Asana Tasks in a dedicated Knowledge Base project. Article body text, category, and author metadata transfer. Article-to-chatbot associations (which articles feed which Leia AI chatbot responses) are internal to Comidor and cannot be extracted. We flag these records in the handoff document and note that the customer must manually reconnect article-to-response logic in their chosen knowledge base tool or AI platform. Knowledge Base article ordering is preserved as task position within the project.

Comidor Contacts and Accounts are separate objects with a many-to-many relationship. Contact records include standard fields plus any attached Custom User Fields. We map Contact-to-Account as a Composed relationship where each Account in Comidor becomes an Asana Organization (workspace-level entity) and each Contact becomes an Asana Contact member attached to that Organization. Contact-to-Account references in Comidor are preserved using a custom field on the Asana Contact that holds the source Account identifier.

Comidor User accounts define permissions, roles, and organizational placement. Teams are groups of Users used in Workflow assignments and process routing. We map Users to Asana workspace members and Teams to Asana Teams. Role and permission scoping in Comidor maps to Asana Team membership levels; full permission parity requires a review of Asana's Admin, Member, Guest, and Limited Access roles against the Comidor role matrix.

Process Scheduling defines automated recurring execution of Workflows or Issue creation in Comidor. This is an execution configuration rather than a data record. We do not migrate schedule configurations. We document every Process Schedule found in the Comidor instance and map each to Asana's repeating task pattern (available on Starter and above) where applicable. Recurring workflow execution has no direct Asana equivalent; the admin rebuilds this as a recurring task or calendar-driven workflow in a separate automation tool.

Comidor's Leia AI chatbot and its configuration (article-to-response mappings, conversation flows, fallback rules) is internal to the Comidor AI layer and cannot be extracted programmatically. We export Knowledge Base articles as text records. The chatbot configuration and the article-to-bot association are flagged for manual rebuild in the customer's chosen AI or knowledge base platform. This is a manual scope item, not a migration limitation of the destination platform.

Comidor collaboration records (calls, emails, meetings, tasks, notes) are exported as structured records where available through the UI. These map to Asana Tasks with TaskSubtype variants (Call, default), Events for calendar-based meetings, and Notes for discussion records. We preserve timestamps, assignee, and content. Attachment handling on engagements follows the same 100MB Asana API limit as Files. Engagements without a matching assignee in the destination are assigned to a migration service account and flagged for reassignment.