Migrate from Propeller CRM to HighLevel

Propeller Contacts map directly to GoHighLevel Contacts. We extract name, email address, phone number, company association, owner email, and any custom fields from the Propeller export. Company association resolves by company name matching: if a matching GoHighLevel Location or Company record exists, we link it; if not, we flag the orphaned contact for customer review. Owner email maps to GoHighLevel user accounts by email match. Any contact where the Propeller owner email has no corresponding GoHighLevel user is flagged in the reconciliation report and held for the customer to provision the user account first.

Propeller Company records map to GoHighLevel Company objects. The relationship between Propeller Contact and Company was maintained by company name matching; we preserve this by re-running the same name-matching logic during GoHighLevel import. If multiple contacts shared the same company name in Propeller, we deduplicate into a single GoHighLevel Company record and link all related Contacts. Address data from Propeller Companies migrates to the GoHighLevel Company address fields.

Propeller Deals map to GoHighLevel Opportunities. Deal name, amount, associated contact, associated company, owner assignment, and current pipeline stage migrate. The deal-to-Opportunity link is resolved by matching the Propeller contact email to the newly created GoHighLevel Contact record. If the Propeller deal referenced a company that was deduplicated, the Opportunity is linked to the consolidated Company record. Closed-won and closed-lost status from Propeller maps to GoHighLevel Opportunity status values.

Propeller pipeline stages were fully customizable by the customer, meaning stage names in the export vary by account. We map Propeller stage names to GoHighLevel pipeline stages during scoping by asking the customer to confirm their stage-equivalent mapping. Stages that have no clear GoHighLevel equivalent (e.g., 'verbal yes' or 'pending docs') require the customer to confirm placement before migration. We create the destination pipeline in GoHighLevel with stages matching the confirmed mapping before record import begins. Propeller stage ordering is preserved if the destination pipeline is configured to use the same sequence.

Propeller Email Campaigns included campaign names, associated contacts, and send dates tracked in the export archive. GoHighLevel does not have a native historical campaign record object; we import campaign metadata as custom fields on the associated Contacts (e.g., last_campaign_name, last_campaign_date) and as notes on relevant Opportunities. The actual automated sequence logic does not migrate — we document the original campaign structure in a written handoff so the customer's admin can rebuild it as a GoHighLevel Workflow.

Propeller email templates with merge field names are mapped to GoHighLevel Email Templates. Template subject lines and body HTML transfer directly. Merge field syntax differs between platforms: Propeller used Gmail-extension-style merge tokens; GoHighLevel uses standard double-brace tokens ({{contact.first_name}}). We convert merge field syntax during the template import so that templates function correctly in GoHighLevel workflows and campaigns from day one.

Propeller user accounts mapped contacts and deals to individual sales representatives by email address. We extract all owner emails from the Propeller archive and attempt to match each against existing GoHighLevel user accounts by email. Any owner email with no corresponding GoHighLevel user is held in the reconciliation queue and flagged with a placeholder user recommendation. The customer provisions these users in GoHighLevel before record import resumes. If a former Propeller team member has left and their account is inactive, their deal and contact assignments are preserved as inactive-owner assignments for the customer to reassign post-migration.

Some Propeller customers built informal custom data structures outside the standard Contact-Deal model using exported spreadsheets maintained alongside Propeller. If the customer has supplementary export files beyond Propeller's standard archive, we assess whether the data maps to GoHighLevel Custom Objects. Custom Objects are available on higher GoHighLevel plan tiers; we confirm the customer's plan supports Custom Object creation before including this scope. Custom Object schema is defined and validated in a GoHighLevel test sub-account before production migration.