Migrate from monday CRM to HighLevel

monday CRM's People feature stores name, email, phone, and CRM properties as a distinct entity accessible via the API. We map People records 1:1 to GoHighLevel Contacts. Email address serves as the dedupe key during import. Any CRM-specific properties stored on the People record (lead source, custom properties) migrate as GoHighLevel Contact custom fields, which must be pre-created in GoHighLevel as Contact-scoped fields before the migration runs.

Deals in monday CRM are Items of CRM type attached to a Pipeline. Each Deal has standard column values (deal value, close date, stage) plus optional custom columns. We map Deals to GoHighLevel Opportunities with monetary values, expected close dates, and stage names preserved. GoHighLevel Opportunity custom fields must be pre-created as Opportunity-scoped fields before migration. Deal owner assignments map to GoHighLevel User by email match.

monday CRM Pipelines contain ordered Stages with optional probability percentages. We read the pipeline definition (stage names, stage order, probabilities) and recreate it as a GoHighLevel Pipeline in Settings before any Deal records are migrated. Stage probability values transfer to the GoHighLevel pipeline stage probability field. The number of monday Pipelines determines how many GoHighLevel Pipelines are configured; multi-pipeline accounts require pipeline mapping as a scoping variable.

CRM boards in monday contain the Pipeline column and associated Deal Items. We extract the board structure as the pipeline container context but do not migrate the board itself as a GoHighLevel object. The pipeline configuration step (see Pipeline mapping) is the destination-side equivalent. Any board-level views (Kanban, Calendar, Chart) are documented for manual rebuild in GoHighLevel since they do not export from monday.

monday CRM supports over 20 column types (text, number, date, formula, status, dependency) on boards. Custom columns attached to Deal Items migrate as GoHighLevel Opportunity custom fields. We read the column definition (name, type, options) during pre-migration scoping and pre-create the corresponding custom field in GoHighLevel. Note that GoHighLevel custom fields are scoped as either Contact or Opportunity and cannot be switched after creation; we confirm scope during scoping based on which record type the column applies to.

Custom columns applied to People records in monday CRM migrate as GoHighLevel Contact custom fields. The same pre-creation requirement applies: we define the field name, type, and options in GoHighLevel before importing People records. monday column types that rely on monday-specific functionality (Formula, Dependency) are recreated as text or number fields in GoHighLevel with a note to the customer on the limitation.

Files uploaded to monday CRM Items or People records are retrieved via monday's file API and re-attached to the corresponding Contact or Opportunity in GoHighLevel. We preserve the original file name, URL reference, and upload date. File attachments are scoped to the primary CRM record they were attached to in monday. Very large attachment volumes (hundreds of files) add to migration timeline and are flagged during scoping.

monday CRM Updates are per-item comment threads accessible via API. We preserve update text and timestamps, mapping them to GoHighLevel Notes attached to the corresponding Contact or Opportunity. GoHighLevel does not have a native threaded comment model equivalent to monday's Updates; Notes provide the closest record-level history. Activity timestamps are preserved as the Note creation date.

monday CRM automations built on the Recipe (Sentence Builder) system or the newer monday workflows system are workflow logic, not CRM data. We do not migrate automations as executable rules. During pre-migration review we capture every active automation definition (trigger, conditions, actions) and deliver it as a written inventory document with GoHighLevel Workflow equivalents documented per rule. The customer's admin rebuilds the automations in GoHighLevel's Workflow builder post-migration. This is a critical scope item for any team with more than five active automations.