Migrate from Referrizer to HighLevel

Referrizer Contacts map to GoHighLevel Contacts with name, phone, email, address, and custom fields transferred directly. We enumerate the custom field schema via the Referrizer paginated API before extraction and create matching GoHighLevel Contact custom fields during the schema design phase. Owner assignment resolves by matching Referrizer owner email to a GoHighLevel User email, with unresolved owners placed in a reconciliation queue for admin provisioning.

Referrizer custom fields are key-value properties on contact records exported via the GET /contacts endpoint. We inspect all custom field names and data types during scoping, create equivalent GoHighLevel Contact custom fields with matching types (text, number, date, dropdown), and preserve field values on each contact record during import. Any multi-select or comma-delimited custom fields map to GoHighLevel multi-select picklists.

Referrizer Deal records map to GoHighLevel Opportunities within a Pipeline. HubSpot-style stage names from Referrizer are recreated as Pipeline stages in GoHighLevel. Deal value, close date, associated contact, and owner assignment migrate directly. The referrer contact on a Referrizer Deal can be linked to the Opportunity as a custom field or tag rather than a native relationship since GoHighLevel Opportunity does not natively track referral source in the same way.

Referrizer Campaigns (Regular and Automated modes) are exported as GoHighLevel Campaigns. Campaign type, status, and contact membership list transfer as a static membership list. Automated campaign triggers and re-entry settings do not migrate as Workflows; we document the trigger configuration in the automation inventory for manual recreation in GoHighLevel's Workflow builder.

Referrizer stores loyalty point balances as numeric custom fields on contact records rather than as a distinct object. We extract these fields during the contact export, separate them from standard contact properties, and remap them to GoHighLevel Contact custom fields (number type) named to reflect the original loyalty program context. If multiple loyalty programs exist, we create one custom field per program. No native loyalty object exists in GoHighLevel without a third-party app.

Referrizer review request history (which contacts received requests, when, and to which platform: Google, Yelp, or Facebook) is stored as activity on the contact record and exported via the activity endpoint. We map this to GoHighLevel's Reputation Management module as a review request log entry, preserving contact name, request date, and target platform. GoHighLevel's reputation workflow must be configured manually post-migration to continue sending new review requests.

Referrizer contact labels are exported as an array on each contact record. We map these arrays to GoHighLevel Tags, which attach to Contacts and allow Smart List filtering. Tags migrate in bulk during the contact import phase. We flag any label names that exceed GoHighLevel's character limits for manual renaming during scoping.

Referrizer Offers and referral link associations are exported as related data on contact records. Offer codes, reward structures, and referral program names are mapped to GoHighLevel Contact custom fields (text type) and optionally tagged with a campaign label for segmentation. Referral tracking beyond this requires manual configuration of GoHighLevel's referral tracking URL parameters or a third-party referral app integration.

Referrizer tracks contact activity events including campaign opens, link clicks, and UTM data via the contact activity endpoints. We export these events as timestamped notes or custom activity log entries in GoHighLevel Contacts, preserving the event type, timestamp, and campaign source. High-volume activity feeds are chunked to avoid API pagination limits. Activity events with no source campaign are logged as generic contact activities.

Referrizer multi-location accounts require location-level scoping during export to avoid pulling contacts from all locations into a single migration bucket. Each location in Referrizer maps to a separate GoHighLevel Sub-Account (on the Unlimited or SaaS Pro plan) or to a separate Pipeline within a single account on the Starter plan. We scope exports by Referrizer location ID, validate contact counts per location, and create the corresponding GoHighLevel account structure before importing contact records into each location's sub-account.