Migrate from Comidor to Microsoft Project

Comidor Issues map to Microsoft Project tasks. The Issue title becomes Task Name; estimated effort or story points become Work (hours); due date maps to Finish date; priority maps to Priority (1-10 scale). If Issues have parent-child nesting, we preserve the hierarchy as summary tasks with WBS numbering. The migration requires the customer to export Issues via Comidor's CSV export function; we transform the CSV into an MPP-compatible XML or CSV interchange format and import through Project desktop or Project Online API.

Comidor Custom User Fields defined globally and attached to Issues transfer as named custom fields on the Microsoft Project task. We extract the field definition (label, type, picklist values if applicable) from the Comidor UI during scoping, then create equivalent custom fields in the destination Project plan using the Field Mapping dialog in Project Desktop or the Project Online REST API. Any picklist-based Custom User Field maps to a custom text or flag field in Project if no equivalent type exists.

Comidor Users and Teams assigned to Issues map to Microsoft Project named resources. We extract the user roster from Comidor during scoping, map each Comidor User to a Project resource with a calendar (Standard is default; the customer's admin updates individual resource calendars post-migration for vacation and availability). Teams in Comidor map to resource groups in Project. If a Comidor Issue has no assignee, we assign it to a placeholder resource and flag for the customer to reassign.

Comidor files and documents attached to Issues migrate as hyperlinks pointing to the original file location in Comidor's file storage during migration, with a note that the customer's admin must move the actual file assets to SharePoint or a designated document management system post-migration. Comidor's file export must be performed manually by the customer before migration begins. We do not extract binary file content; we extract URLs and file metadata only.

Comidor Workflows modeled in BPMN 2.0 are not migratable as code. Microsoft Project has no native workflow execution engine. We extract the full workflow configuration as a structured BPMN package (including conditions, gateways, assigned roles, and escalation paths) and deliver it as a written document with recommended Power Automate triggers and actions for each workflow step. The customer's admin rebuilds automated routing and approval chains in Power Automate post-migration. This is documented separately from the data migration scope.

Comidor Knowledge Base articles export as text records with category assignments. Article-to-chatbot associations (Leia AI configuration) cannot be extracted and are not migratable. We deliver the article content as a structured CSV with category metadata. The customer's admin imports articles into a SharePoint library or Teams Wiki manually. If the Knowledge Base was used as a reference source for Issues, we flag which articles are referenced so they can be relinked post-migration.

Comidor Apps define the data structure and UI for a business process. Each App that contains Issues maps to a separate Microsoft Project plan or a subproject within a master project. We document the App structure (forms, fields, related objects) during scoping and map it to the equivalent Project plan structure (task fields, custom fields, resource assignments). Apps without Issues (standalone data collection apps, RPA configurations) are documented as out-of-scope with a recommendation for SharePoint Lists, Dataverse, or Power Apps as alternatives.

Comidor User Forms (data entry interfaces with conditional logic) do not have a Microsoft Project equivalent. We extract form definitions as structured schema documentation, including field types, picklist values, and conditional show/hide rules. This becomes part of the Power Apps rebuild guide for the customer's admin if the forms represent business process data entry that must be preserved.

Comidor Process Scheduling defines recurring workflow executions and automated Issue creation on a cron-like schedule. This is an execution configuration, not a data record, and is excluded from migration scope. The customer documents recurring project kickoff or status workflows during scoping and rebuilds them as Power Automate scheduled flows post-migration.

Comidor Contacts and Accounts map to Microsoft Project resources as extended resource properties (Name, Initials, Group, Email). We extract the contact roster during scoping and create resource records with email addresses so that the Project Online integration can resolve assignment notifications through Microsoft 365. Full CRM-level contact data (addresses, deal associations) does not apply in a project scheduling context and is noted as out-of-scope.