Migrate from FreeCRM to HighLevel

FreeCRM Contact records export via CSV with standard fields (name, email, phone, address) and template-driven custom fields unique to the account. We inventory the full template field set during discovery, map each to a GoHighLevel custom field on the Contact object, and load through the GoHighLevel API v2 Contacts endpoint. Tags export as comma-separated values and are split into GoHighLevel tags during import. Owner assignment maps by email to the GoHighLevel user reference where present.

FreeCRM Company records carry name, domain, industry, and address fields that map into the Company Info section of a GoHighLevel Contact. The FreeCRM contact-to-company parent-child relationship is preserved by linking the Contact record to a primary Company record in GoHighLevel. We use the company name or domain as a deduplication key during import.

FreeCRM Lead records use the template system so field names vary per account. We extract the full field set during discovery, identify the lead status and source fields, and map them to GoHighLevel Contact custom fields. If FreeCRM records carry an explicit lead-to-contact lifecycle indicator, we use that to split records into GoHighLevel Contacts in a pre-conversion state versus fully converted contacts with opportunity associations.

FreeCRM Deals include amount, stage, expected close date, and related contact. Stage values are stored as free text (account-defined Kanban columns) rather than a structured stage object. We extract the complete stage list from FreeCRM during discovery, map each to a corresponding GoHighLevel pipeline stage column, and create the GoHighLevel pipeline structure before deal records load. Amount and expected close date transfer directly to the GoHighLevel Opportunity monetary and date fields.

FreeCRM's Kanban board stages are account-defined text values with no standardized stage object. We pull the full stage list from the FreeCRM export, map each stage name to a GoHighLevel pipeline stage, and configure stage probabilities based on the stage order. The GoHighLevel pipeline must be created before any Opportunity records import because Opportunity.pipelineId is a required reference.

FreeCRM exports activity records as a flat list with type, description, related contact or company, and timestamp. Tasks map to GoHighLevel Tasks; meeting and event records map to GoHighLevel Appointments. The related-to link (Contact or Company) resolves by matching the FreeCRM contact name or email to the GoHighLevel Contact created in the first import phase. Historical activity sequencing is preserved by setting the GoHighLevel timestamp to the original FreeCRM timestamp.

FreeCRM custom fields are defined per-record via templates and vary by account. Every custom field in the active template set is inventoried during discovery, typed (text, number, date, picklist, checkbox), and created as a GoHighLevel Custom Field on the appropriate object (Contact, Company, or Opportunity) before data import begins. Template field names are mapped to GoHighLevel custom field API names during the discovery phase to prevent silent field drops.

FreeCRM exports tags as comma-separated values on Contact and Company records. We split the comma-separated values into individual GoHighLevel tags during import and attach them to the corresponding Contact record via the GoHighLevel Tags API endpoint. Tags used for lead source classification are kept distinct from tags used for workflow segmentation to support both reporting and automation use cases in GoHighLevel.

FreeCRM User accounts exist but owner assignment on records is not consistently populated across all accounts. We extract every distinct owner email referenced on Contact, Company, and Deal records and match by email to GoHighLevel Users. Any FreeCRM owner without a matching GoHighLevel User goes to a reconciliation queue for the customer's admin to provision before the record import phase. This lookup step is blocking for deal and contact imports that carry owner references.

Invoice creation is a FreeCRM Pro feature. If the customer has invoice data on the free tier (tracked manually or exported from another source), we migrate the invoice records as standalone GoHighLevel Custom Object entries. GoHighLevel does not have a native Invoice object at the Starter tier, so invoice data lands in a purpose-built Custom Object with line item fields, total, status, and associated Contact lookup.