Migrate from Comidor to monday Work Management

Each Comidor App built in App Designer maps to a monday.com Board, or to a dedicated Workspace if the app represents a separate business unit. Within the board, Comidor app sections map to Groups, and app records map to Items. Custom column types defined in the Comidor App Designer translate to monday.com column types (text, number, date, status, dropdown, formula). Complex app logic, sub-forms, and conditional visibility rules do not migrate and are documented for manual rebuild. App Designer configurations are captured as structured schema packages and as a written board design guide.

Comidor BPMN 2.0 workflow definitions are extracted as portable configuration packages. In monday.com, automated task assignments, conditional routing, and escalation triggers translate to automation recipes and item dependency rules. Multi-branch BPMN conditions with timers, parallel paths, or external system calls cannot be represented in monday.com's automation model and are flagged in the workflow inventory as requiring manual redesign or a third-party integration (Zapier, Make) to replicate the full logic.

Comidor Issues are the primary work record and map directly to monday.com Items. Issue status, priority, assignee, due date, description, and custom field values translate to corresponding Item columns. Issue-to-Contact and Issue-to-Account links translate to monday.com person columns or connected boards depending on the relationship cardinality. Closed/open status maps to Item archive state or a status column value.

Comidor Contacts map to monday.com person records if the monday CRM product is active, or to Items in a dedicated People board if using monday.com Work Management. Contact fields (name, email, phone, address) map to monday.com text and contact columns. Custom User Fields attached to Contact records map to monday.com column types with type coercion (multi-select to dropdown, date to date column, number to number column). Contact-to-Account relationships with many-to-many cardinality require a junction board or monday.com's Relations column type.

Comidor Accounts map to monday.com Groups within a People board (if monday CRM is active), or to a separate Accounts board if using Work Management. Account fields map to monday.com column types, with the account name as the primary text. The many-to-many relationship between Contact and Account in Comidor resolves to monday.com's Relations column or a linked board pattern depending on the relationship complexity.

Comidor files and documents stored as attachments or standalone content management records migrate as file attachments on the corresponding monday.com Items. We extract binary files and associated metadata (filename, size, upload date, uploader) and attach them to the target Item. Storage tier restrictions from Comidor (if on a limited plan) may affect what files are accessible for export; we audit storage limits during scoping. monday.com's file storage limits per plan (500 MB on some tiers) are reviewed and flagged if the migrated file volume exceeds the destination plan allowance.

Comidor Custom User Fields are globally reusable across multiple objects and are referenced inside Workflows and User Forms. We extract field definitions first in the migration sequence before any object records, because the field must exist before any record referencing it can be valid. Each Custom User Field maps to a monday.com Column of the closest equivalent type: text fields map to text columns, picklists to dropdown or status columns, numbers to number columns, dates to date columns, and multi-select to multi-select dropdown columns. Fields with cross-object references (lookup to another object) map to monday.com's Connect Boards column or a relation column with a note that manual board linkage is required.

Comidor User Forms embed Custom User Fields and are used inside Workflows for data entry. Form field definitions map to monday.com board column configurations. Conditional show/hide logic within Comidor forms (based on field values) has no direct monday.com equivalent; these are documented in the handoff package as column dependency configurations where monday.com supports them (column dependencies between fields), or flagged as requiring manual workflow or integration-based alternatives.

Comidor Knowledge Base articles export as text-based records with category assignments and article body content. Articles map to Items in a dedicated monday.com board organized by category groups, or to monday.com Docs if the customer licenses that product. Article-to-article links, article-to-Leia chatbot associations, and any AI-driven response mapping are internal to Comidor and cannot be extracted; these are flagged in the handoff package as requiring manual review and bot reconfiguration using a third-party AI integration if the customer requires chatbot functionality at the destination.

Comidor User accounts (name, email, role, team membership) map to monday.com User accounts. We match users by email address. Team membership in Comidor translates to monday.com Teams if the customer uses monday.com's team management features, or to Workspace membership at the board level. Any Comidor user without a matching monday.com account goes to a reconciliation queue for the admin to provision before record import.

Comidor Teams are groups of Users used in Workflow assignments and process routing. They map to monday.com Teams (available on Pro and Enterprise plans). If the destination monday.com plan does not include Teams, team membership maps to Workspace-level board sharing permissions or is documented as requiring manual assignment after migration.

Comidor Process Scheduling configurations are execution settings (recurring workflow triggers, automated Issue creation intervals) and are not data records, so they cannot be exported as data. We extract the schedule configurations as written documentation during discovery and map each one to a monday.com Automation with a scheduled trigger. The customer rebuilds these in monday.com using our documented equivalent; they do not migrate as code.