Migrate from LeadMaster to HighLevel

LeadMaster Accounts map to GoHighLevel Contacts with the company_name stored in the Contact's business name field and the address data mapped to the Contact's address fields. We create a Company record in GoHighLevel first and link the Contact to it via the company_name association. Custom fields on the LeadMaster Account (industry classification, employee count, annual revenue) map to GoHighLevel custom fields created against the Contact object before import. If the customer uses LeadMaster's primary contact link, we map that Contact as the primary Contact record linked to the Company.

LeadMaster Leads are the primary data object and map directly to GoHighLevel Contacts. The LeadCenter export includes owner assignment, lifecycle status, lead source, rating, and all standard and custom properties. We map LeadMaster's lead_status and rating fields to GoHighLevel Contact custom fields of equivalent type. Owner assignment resolves via email match against GoHighLevel users provisioned before migration. Historical timestamps (created_date, last_modified_date) preserve on the Contact record.

LeadMaster Opportunities map to GoHighLevel Pipeline Deals. Stage, amount, expected close date, probability (if populated), owner, and associated Account/Lead link migrate directly. We pre-configure GoHighLevel pipeline stages to match the LeadMaster opportunity pipeline before import so that stage names and probability percentages are consistent post-migration. Custom opportunity fields map to GoHighLevel custom fields against the Deal object.

LeadMaster Cases (help desk module) map to GoHighLevel Tasks with a custom status field flagging them as Cases, or to a GoHighLevel Custom Object named Cases if the customer prefers a dedicated object type. Case number, status (open/pending/closed), priority, description, and associated Account/Contact link preserve. Conversation threads in Cases migrate as Notes linked to the parent Task or Custom Object record. We determine the Case strategy during scoping based on the customer's post-migration support workflow.

LeadMaster custom form submissions stored against Leads or Accounts map to GoHighLevel Contact custom fields. We inventory every form field definition during discovery, create matching custom fields in GoHighLevel before import, and map form submission values to the corresponding Contact record. Where a form field has no GoHighLevel equivalent, we fall back to a structured notes field or a JSON-embedded custom field to preserve the data without losing schema context.

LeadMaster marketing campaigns with associated contact lists map to GoHighLevel Campaigns. Campaign name, status, start/end dates, budget, and type migrate. Contact associations from the campaign member list map to GoHighLevel Campaign contacts. Email template content migrates as exported HTML files that can be re-imported into GoHighLevel's email builder. Automated sequences tied to campaigns do not migrate; we document each campaign's automation logic in the workflow inventory for rebuild in GoHighLevel's workflow builder.

LeadMaster landing page templates and content are exported as HTML during migration. The page hosting and form-to-lead routing must be re-established in GoHighLevel's Funnel builder. We deliver the exported HTML content and a mapping table showing which GoHighLevel funnel steps replace each LeadMaster landing page. The form field mappings from the custom form mapping step carry through so that form submissions land in the correct GoHighLevel Contact custom fields.

LeadMaster user accounts and their roles and active/inactive status map to GoHighLevel users. We resolve owners by email match. Any LeadMaster Owner without a matching GoHighLevel user is held in a reconciliation queue for the customer's admin to provision before record import resumes. Active users on LeadMaster become active GoHighLevel users; inactive users are created as inactive to preserve the assignment history on historical records.

LeadMaster notes attached to Leads, Accounts, or Opportunities migrate to GoHighLevel Notes linked to the corresponding Contact or Deal record. Note body and creation timestamp preserve. Notes created by inactive users on LeadMaster carry the original author's name in the Note record to maintain attribution history.

LeadMaster logged calls, emails, and calendar events migrate to GoHighLevel Activity records. Call duration and disposition map to custom Task fields. Email subject and body map to Note records linked to the Contact. Calendar events with start/end times map to GoHighLevel Calendar Events with invitee data preserved. Activity timestamps (created_date) preserve to maintain the chronological timeline in GoHighLevel's activity feed.

LeadMaster Smart Queue definitions and saved filter criteria are documented during discovery. We deliver a mapping table showing which GoHighLevel Contact List views, tags, or smart list filters reproduce each Smart Queue result. The filter logic itself must be re-implemented in GoHighLevel's filter builder; we provide the criteria inputs so the customer's admin can reconstruct the views without reverse-engineering the original filters.

File attachments stored against LeadMaster Leads, Accounts, or Opportunities are exported and re-uploaded to GoHighLevel, preserving their association to the parent Contact or Deal record. We flag large-volume attachment sets (over 500 files) during scoping so that the customer can decide whether to migrate all attachments or prioritize recent records. Attachments exceeding reasonable migration volume are flagged with a storage plan recommendation.