Migrate from GENIEE to HighLevel

GENIEE SFA/CRM Contacts map to GoHighLevel Contacts. We resolve Japanese field labels to English equivalents during scoping using machine-assisted translation and Japanese-speaking engineers, mapping contact name fields, email, phone, address, and custom properties to their GoHighLevel counterparts. Owner assignment resolves by matching GENIEE owner email to GoHighLevel User email.

GENIEE Companies map to GoHighLevel Accounts. Japanese regional naming conventions (prefectures, ward codes) and department hierarchy data migrate as custom fields on the Account record. We preserve the Account-Contact linkage from GENIEE and rebuild it in GoHighLevel where Accounts serve as groupings rather than primary record containers.

GENIEE Deals map to GoHighLevel Opportunities inside Pipelines. Pipeline stages from GENIEE become GoHighLevel Pipeline stages with probability percentages converted to integer values. Deal value, close date, and stage history transfer directly. We configure the GoHighLevel Pipeline before migration to match the GENIEE stage structure.

GENIEE MA Campaigns migrate to GoHighLevel Campaigns. UTM parameters, source/medium attribution data stored per Contact normalizes to GoHighLevel's campaign tracking fields. Campaign-Customer association migrates as CampaignMember records. Attribution models from GENIEE MA do not have a direct GoHighLevel equivalent and are documented for the customer to configure post-migration.

GENIEE DSP campaign metadata (budget, targeting parameters, ad formats, flight dates, bid logs) does not map to any standard GoHighLevel object. We export DSP campaign records as a GoHighLevel Custom Object with fields named to match the original DSP schema, so the customer's team can reference the data without a full schema redesign. This is SSP/DSP-specific and not a standard CRM migration object.

GENIEE SSP publisher inventory data (slot IDs, floor prices, telco/mobile/desktop classifications) has no GoHighLevel equivalent. We export inventory configuration as a Custom Object labeled 'Ad Inventory' with original field names preserved, enabling the customer's team to cross-reference DSP campaign data without a separate SSP tool.

GENIEE SFA/CRM Users (record owners with email, name, and role) migrate to GoHighLevel Users. We match by email address. Any GENIEE owner without a matching GoHighLevel User is held in a reconciliation queue for the customer's admin to provision before Contact and Deal import proceeds.

Attachments on GENIEE Contacts, Accounts, and Deals export as binary files and re-upload to GoHighLevel as file attachments linked to the corresponding Contact, Account, or Opportunity record. Original file names, MIME types, and upload timestamps are preserved. File size and type limits follow GoHighLevel's tenant-specific constraints.

GENIEE tenant-specific custom fields on Contacts and Accounts are discovered during scoping, and the full custom property list generates a field map. We create equivalent custom fields in GoHighLevel before data import, handling type conversion (text, number, date, picklist) and preserving the original Japanese field labels in a description or tooltip for reference.

GENIEE tags on Contacts and Companies export as label arrays. GoHighLevel supports Tags on Contacts which we populate from the GENIEE export. Tag vocabulary is tenant-defined and migrates as-is; no value transformation is applied unless duplicate tags with different casing are detected and normalized during import.