Migrate from Genoo to HighLevel

Genoo Leads map directly to GoHighLevel Contacts. All standard fields (first name, last name, email, phone, company, website, source) transfer via CSV. GoHighLevel uses a unified Contact model rather than separate Lead and Contact objects, so the Genoo Lead qualification status does not have a direct equivalent; we preserve it in a custom field genoo_lead_status__c for reporting. Email address is the primary dedupe key during import.

Genoo Contacts map to GoHighLevel Contacts. Where the destination GoHighLevel account uses a unified Contact model, the Genoo Contact and Lead objects combine into a single Contact record using email as the dedupe identifier. Custom properties on Genoo Contacts migrate to GoHighLevel custom fields which we create during the schema design phase.

Genoo Account records link to Leads and Contacts with company name, website, and industry. GoHighLevel does not have a separate Account or Company object in its standard CRM model; company information lives as fields on the Contact record. We map Genoo Account company_name to the Contact's Company field and website to the Website field. If the customer requires a separate Company object, we document the need during scoping and configure a custom object to preserve the Genoo Account relationship model.

Genoo Opportunities are derived from CRM sync rather than native first-class objects; they represent pipeline stages synced from an external CRM. We import the Opportunity association record (opportunity name, stage, value, close date, owner) as GoHighLevel Opportunities. GoHighLevel's Opportunity object includes pipeline stages, monetary value, and contact associations that map directly from Genoo's Opportunity fields.

Genoo Campaigns represent drip nurture programs with name, status, start/end dates, and associated program steps. We map Campaigns to GoHighLevel Campaigns, preserving program name, status, and the drip sequence membership (which Contacts entered which program and when). Campaign membership links migrate as Campaign Member records in GoHighLevel, resolved by email match against the Contact table.

Genoo tracks which Leads entered which Campaign drip sequence and the enrollment date. We import this as Campaign Member records in GoHighLevel with the Contact lookup resolved by email address at migration time. If the drip sequence had multiple steps, we document the step order and enrollment timestamp in custom Campaign Member fields. Step completion data migrates as enrollment records.

Event registrations in Genoo are stored as Activity-type records linked to Leads. We import registration data (event name, registration date, registration status, attendance status where available) as custom Activity records in GoHighLevel linked to the Contact. Post-event attendance records migrate separately as a second wave if they are available in the Genoo export.

Genoo landing pages and microsites are stored as HTML template blobs. We extract page name, URL slug, and form field configuration as structured data where available. Full page rendering assets do not map cleanly to GoHighLevel's funnel builder because Genoo uses a different templating model. We deliver a page inventory document listing every active landing page with its URL, form fields, and submission volume so the customer's team can manually rebuild in GoHighLevel's funnel builder.

Genoo email templates are HTML-based with subject lines and body content. We extract the template name, subject line, and HTML body. Modern email builders in GoHighLevel use block-based editors that do not map cleanly from raw HTML templates; we preserve the template content in a structured format and advise customers to copy the key content into GoHighLevel's drag-and-drop email editor rather than importing the raw HTML directly.