Migrate from Bloomr to HighLevel

Bloomr Contacts map to GoHighLevel Contacts. Standard fields (first name, last name, email, phone, address) migrate directly. Any custom fields discovered during Bloomr data profiling are mapped to GoHighLevel field types (text, number, date, dropdown, checkbox). GoHighLevel Contacts are scoped to a Location parent; we create or resolve the Location reference before Contact import using the Company-to-Location mapping as the parent lookup key.

Bloomr Companies map to GoHighLevel Locations, which serve as the organizational container for all CRM records. Company name becomes Location name; domain becomes Location website; industry and address fields map to the corresponding Location address and custom field slots. GoHighLevel uses Locations to organize contacts, opportunities, and pipelines, so this is the first object created in any migration because all subsequent objects reference it.

Bloomr Deals map to GoHighLevel Opportunities. Deal name maps to Opportunity name; deal value maps to Opportunity value; stage maps to a GoHighLevel stage value within a configured pipeline. Owner assignment resolves by email match to a GoHighLevel User. Contact associations from Bloomr Deals migrate as Opportunity contact links resolved through the Contact migration. Bloomr custom deal fields become Opportunity custom fields.

Bloomr Activity records (calls, emails, meetings, tasks, notes) map to GoHighLevel Activities. GoHighLevel stores all engagement types in a unified Activity object with a type property distinguishing calls, emails, meetings, tasks, and notes. Activity date, subject, notes content, and linked contact reference migrate directly. Activity timestamps preserve the original Bloomr creation date for timeline integrity.

Bloomr Users map to GoHighLevel Users. Name, email, role, and permission scope resolve by email match. Owner assignments on Deals and Activities reference these User records. Any Bloomr User without a matching GoHighLevel User is placed in a reconciliation queue for the admin to provision before record import resumes, because OwnerId references must be valid at migration time.

Bloomr custom fields are discovered during the API exploration and data profiling phase. Each custom field is mapped to the closest GoHighLevel field type (text field, number field, date field, dropdown, multi-select dropdown, or checkbox). Bloomr picklist values are translated to GoHighLevel dropdown options. Custom fields on Companies, Contacts, and Deals migrate to the corresponding GoHighLevel Location, Contact, or Opportunity custom field equivalents.

Bloomr pipeline stages are recreated as GoHighLevel Pipeline stage values. Each Bloomr pipeline becomes a GoHighLevel Pipeline with its own stage sequence, stage probabilities, and stage names. If Bloomr has multiple pipelines, we create corresponding GoHighLevel Pipelines and map stage values so that deal history reflects the original pipeline context. Stage probability percentages migrate from Bloomr to GoHighLevel stage values.

Attachment migration is conditional on API exploration confirming file access endpoints in Bloomr. If file endpoints are confirmed, attachments linked to Contacts, Companies, or Deals migrate as ContentDocument records attached via ContentDocumentLink to the parent record. If no API access to files is confirmed, we exclude attachment migration from standard scope and flag it for manual export from the Bloomr UI during migration week.

Bloomr workflow and automation data does not migrate. No export mechanism is documented for Bloomr automated rules, lead routing logic, or sequence configurations. We provide a workflow audit template during scoping for the customer's admin to document existing automations manually. The resulting inventory maps each Bloomr automation to a recommended GoHighLevel Workflow equivalent for manual rebuild post-migration.

If Bloomr data profiling reveals custom objects beyond the standard Contacts, Companies, and Deals, those map to GoHighLevel Custom Objects. We pre-create the destination schema including all custom fields, lookup relationships, and field types before importing any data. Bloomr custom object records import via GoHighLevel's custom object API endpoints after all standard objects are migrated and their primary keys are available for relationship resolution.