Migrate from MiniCRM to HighLevel

MiniCRM Cards are the primary record container and may hold both person-level details and deal information. We split at migration time: Card fields that are person attributes (name, email, phone, address) map to GoHighLevel Contact; Card fields that describe a sale (deal value, stage, expected close date) map to GoHighLevel Opportunity. The split rule is defined during scoping based on the customer's Card structure. The original MiniCRM Card ID is preserved in a custom field minicrm_card_id__c for reconciliation.

MiniCRM Contact sub-records map directly to GoHighLevel Contact. Standard fields (name, email, phone, address) migrate cleanly. We use email as the dedupe key during import. If a Contact sub-record has no email, we use first name + last name as the dedupe criterion.

MiniCRM Company records hold business-level data. GoHighLevel does not have a native Company/Account object separate from Contact, so company details (company name, industry, website, size) migrate to the primary Contact record's company-related fields. If the customer uses Companies as standalone entities linked to multiple Contacts, we recommend creating a Custom Object called Company in GoHighLevel and linking Contacts via a lookup relationship.

MiniCRM Deals (called Interests) map to GoHighLevel Opportunities. The deal value, pipeline stage name, expected close date, and associated owner migrate. MiniCRM pipeline stages are mapped to GoHighLevel pipeline stages during schema setup. We resolve the parent Contact reference at migration time.

MiniCRM pipeline stages map to GoHighLevel pipeline stages. We create the GoHighLevel pipeline before migration, define stage names that match the customer's MiniCRM stage names, and set stage probabilities. Stage ordering is preserved from MiniCRM.

MiniCRM Tasks migrate to GoHighLevel Task. Due date, status, assignee (resolved via User mapping), and description transfer directly. Recurrence patterns and reminder settings do not export and are flagged for manual configuration in GoHighLevel.

MiniCRM Notes attached to Cards migrate as GoHighLevel Notes linked via ContentDocumentLink to the parent Contact or Opportunity. Note body transfers as rich text. We preserve the association to the original Card for reconciliation.

MiniCRM custom fields on Cards migrate to GoHighLevel Contact Custom Fields (for person attributes) or Opportunity Custom Fields (for deal attributes). Field types are mapped: text to text, number to number, date to date, choice/dropdown to dropdown. Choice field values are mapped individually to the GoHighLevel dropdown options during schema setup.

MiniCRM automation rules cannot be exported via API. We document every active automation during discovery with its trigger, conditions, actions, and execution order. The customer rebuilds these in GoHighLevel's Workflow builder. We prioritize documenting revenue-impacting sequences (deal stage triggers, follow-up emails) first.

MiniCRM Users map to GoHighLevel Users. We resolve by email match. Any MiniCRM User without a matching GoHighLevel User is held in a reconciliation queue for the customer's admin to provision before record import resumes.

MiniCRM calendar events linked to Cards migrate as GoHighLevel Appointments. Event title, date, time, and linked Contact transfer. Full attendee lists and calendar-specific metadata require supplemental mapping during scoping.

Tags applied to MiniCRM Cards for segmentation migrate as GoHighLevel Tags on the corresponding Contact or Opportunity. We deduplicate tags during import to avoid recreating messy taxonomy in the new system.