Migrate from noCRM.io to HighLevel

noCRM Leads are the central object with status values (Won, Lost, Cancelled, To-Do, Standby), tags, assigned users, comments, custom field values, and an activity log. We apply a status-based split during migration: Leads with status Won or Lost map to GoHighLevel Contact (the deal is concluded and the contact relationship persists). Leads with status To-Do or Standby map to GoHighLevel Lead (the prospect is still active and should enter the GoHighLevel pipeline as a new Opportunity). Cancelled leads map to GoHighLevel Contact with a status tag. The original noCRM status and all Predefined Field values migrate into GoHighLevel custom fields for audit.

noCRM Pipeline Steps define the stages within a Pipeline. Each Lead occupies exactly one Step at a time, and step transitions are logged in the activity history. We map each Step to a GoHighLevel Pipeline Stage with the same relative position (Step 1 becomes Stage 1, Step 2 becomes Stage 2, etc.). Step-transition timestamps migrate as Notes on the Contact or Lead so the progression timeline is preserved in GoHighLevel even though the transition itself is not a native stage-history object.

noCRM Pipelines contain Pipeline Steps and group Leads by sales process (e.g., Inbound vs Outbound). Expert and Dream accounts can have multiple Pipelines; Starter is limited to one. We export all Pipelines and their Steps, then recreate each as a GoHighLevel Pipeline. Starter accounts with one Pipeline map directly to one GoHighLevel Pipeline. The customer configures GoHighLevel pipeline probability values per stage after migration.

Prospecting Lists group Leads for outbound campaigns and reporting. noCRM's list membership is stored as a relationship rather than a tag. We export list membership and decide with the customer during scoping whether to map each Prospecting List to a GoHighLevel Static List (for campaign targeting) or to a Tag applied to each Contact or Lead (for segmentation). Some lists may represent lead sources and map to GoHighLevel's contact source field instead.

Tags in noCRM are freeform labels applied to Leads for categorization. We preserve all tags as-is and map them directly to GoHighLevel Tags. GoHighLevel Tags are applied at the Contact or Lead level and can be used for filtering, automation triggers, and reporting. Duplicate tags from noCRM merge automatically in GoHighLevel's tag deduplication.

Each noCRM Lead carries a chronological activity log capturing comments, status changes, step transitions, and manual entries. We export the activity log as a structured timeline and map it to GoHighLevel Notes attached to the corresponding Contact or Lead record. Notes are sequenced by timestamp so the rep sees the full conversation history on the contact record. Automation-triggered entries are flagged in the Note body.

Files attached to noCRM Leads are exported as binary blobs via the REST API (available on Expert and Dream tiers; Starter has no API access). We preserve the original file name and attachment reference and re-attach them to the corresponding GoHighLevel Contact or Lead record. Attachments exceeding GoHighLevel's file size limits are flagged and delivered as a downloadable archive with mapping references.

noCRM Users are assigned to Leads and own Pipeline activity. We map User accounts by email match to GoHighLevel Users. Role and permission structures in noCRM (admin vs standard user) do not transfer directly; the GoHighLevel admin reconfigures User roles post-migration. Users in noCRM without a matching GoHighLevel account go to a reconciliation queue for the admin to provision before record import completes.