Migrate from Cirrus CRM to HighLevel

Cirrus CRM Contacts map directly to GoHighLevel Contacts. Standard fields (name, email, phone, address) map to their GoHighLevel equivalents. Custom fields migrate to GoHighLevel custom fields created before import, with field types validated (text, number, date, picklist) against a 50-record test batch first. Contact-to-Company relationship migrates via the GoHighLevel Contact's assigned Location or Company field. Owner assignment resolves by email match against GoHighLevel Users.

Cirrus CRM Companies map to GoHighLevel Locations attached to a Company record. Credit information and geographic enrichment from Cirrus CRM migrate to custom fields on the GoHighLevel Company or Location object since GoHighLevel does not have native credit scoring. Company serves as the parent record so that multiple Locations can be attached if the customer uses branch or subsidiary structures in Cirrus CRM.

Cirrus CRM Deals map to GoHighLevel Opportunities. The dealstage property maps to GoHighLevel pipeline stage. Deal monetary value (amount) maps to the Opportunity value field. We preserve historical stage movement as GoHighLevel Pipeline Activity entries or as a custom JSON field if the customer requires full stage history audit. Closed-Lost and Closed-Won reasons from Cirrus CRM custom fields migrate to GoHighLevel custom fields on the Opportunity.

Cirrus CRM Quotes carry line items and product associations. We map each Quote to a GoHighLevel Opportunity with line items representing the quote lines. The Opportunity value sums from the quote lines automatically. If a Quote has multiple line items referencing different products, all line items merge into the single Opportunity record in GoHighLevel. Quote-to-Deal linkage (if the Cirrus CRM Quote references a parent Deal) maps to a GoHighLevel Opportunity with a custom field crm_quote_id__c preserving the source reference.

Cirrus CRM Orders are generated from Quotes and linked to ERP records. Since GoHighLevel has no standalone Order object, each Order maps to the parent Opportunity's line items with a flag crm_order_source__c = 'erp_linked' to indicate ERP origin. If the Order references an ERP invoice number, that value migrates to a custom Opportunity field erp_invoice_ref__c. We flag any Order whose ERP sync status is broken or stale before migration so the customer can decide whether to include or exclude it.

Cirrus CRM pipeline definitions (stage names, order, probabilities) are not stored on deal records but in a separate pipeline configuration. We extract the pipeline definition from Cirrus CRM during discovery, then configure the corresponding GoHighLevel Pipeline with matching stage names and probabilities. If the customer uses multiple Cirrus CRM pipelines, each becomes a separate GoHighLevel Pipeline assigned to the appropriate Opportunity type or workflow.

Cirrus CRM Activities (calls, emails, meetings, tasks) linked to Contacts and Deals map to GoHighLevel Contact timeline entries. Call disposition, duration, and recording URL transfer to GoHighLevel custom activity fields. Activity timestamp preserves the original Cirrus CRM timestamp to maintain timeline ordering. Since GoHighLevel timeline entries do not support bulk CSV import for historical activities, we use GoHighLevel's API with batch injection and rate-limit handling to insert activity records.

Cirrus CRM Campaigns track objectives and campaign-level metrics. We migrate campaign names and statuses to GoHighLevel Campaigns or as Tags on relevant Contacts, depending on whether the customer uses GoHighLevel's campaign tracking features. Individual campaign member associations (which Contacts belong to which Campaign) migrate as GoHighLevel Campaign membership records or as Tag assignments, confirmed during scoping.