Migrate from BSI CRM to HighLevel

BSI CRM contact records with standard fields (name, email, phone, title) and any discovered custom properties map directly to GoHighLevel Contact records. We extract the full field list during BSI's discovery phase, map each to a GoHighLevel Contact custom field or native field, and load via GoHighLevel's Contacts API. Email address is used as the dedupe key. BSI contact ownership maps to GoHighLevel Assigned To (user reference) after Owner reconciliation.

BSI CRM company/account records map to GoHighLevel Company records. BSI's hierarchical company structures and parent-child relationships map to GoHighLevel's Company parent field. Industry classification fields from BSI become GoHighLevel Contact or Company custom fields depending on where the customer stores industry data. Company records are loaded before Contact records so that the Company lookup is satisfied at Contact insert time.

BSI CRM Deal records carry pipeline stage, deal value, owner assignment, and expected close date. Pipeline stages require explicit mapping because BSI's stage names and counts vary by industry configuration — healthcare deals have different stages than banking or retail. We document the existing stage names and probabilities during discovery, configure matching GoHighLevel pipeline stages, and map the stage values before any deal data moves. Closed-Lost and Closed-Won statuses from BSI translate to GoHighLevel pipeline status values.

BSI CRM pipeline configurations map to GoHighLevel Opportunity Pipelines. Each BSI pipeline becomes a GoHighLevel pipeline with stages, probabilities, and categories configured to match the original. GoHighLevel's visual pipeline builder accepts the stage names and order from BSI directly. If the customer uses BSI's industry-specific pipeline templates, we document those as part of the discovery output and replicate them in GoHighLevel's pipeline settings.

BSI CRM logged calls map to GoHighLevel Contact activity records. Call duration, disposition, timestamp, and outcome transfer to GoHighLevel custom activity fields. Parent contact linkage is preserved by resolving the contact's GoHighLevel ID at migration time. If BSI stores call recordings, the file references are flagged for manual re-upload since file storage paths differ between platforms.

BSI CRM logged email engagements migrate to GoHighLevel activity history attached to the relevant Contact record. Email subject, body content, direction (sent/received), and timestamp transfer. Email thread linkage is not preserved as a native GoHighLevel feature; we document thread grouping by date and contact for the customer's admin to reassemble if needed.

BSI CRM meeting records migrate to GoHighLevel Contact activities with meeting title, date, duration, and attendees preserved. Attendee information is stored as a custom text field or linked via contact references. Calendar integrations (Cal.com, Calendly) used in GoHighLevel are configured post-migration rather than migrated from BSI.

BSI CRM task records map to GoHighLevel Tasks attached to the relevant Contact or Opportunity. Task status, priority, due date, and description transfer directly. Task assignment resolves BSI owner references to GoHighLevel user assignments during migration. Completed task history is preserved as activity records even though GoHighLevel's native task UI focuses on open tasks.

BSI CRM custom objects and fields require pre-migration discovery to enumerate — the platform does not publish a self-service export for custom schema. We perform manual discovery to list every custom object name, field definition, and record count. These map to GoHighLevel Contact Custom Fields or Opportunity Custom Fields depending on which object the data logically belongs to. GoHighLevel distinguishes between Contact and Opportunity custom fields and does not allow switching a field's type after creation, so the classification must be correct before migration begins.

BSI CRM user and owner records are migrated first in the load sequence because all other objects reference them as foreign keys. We preserve the user's email, name, and role designation from BSI and map to GoHighLevel user accounts. BSI role and permission sets do not transfer — GoHighLevel's permission model is structured differently and requires manual configuration post-migration by the customer's admin team.

BSI CRM tagging and custom classification fields that do not have a direct GoHighLevel equivalent are captured as GoHighLevel Tags. Multi-value tags from BSI map to multiple GoHighLevel tag assignments on the Contact record. Classification fields stored as picklist values in BSI become single-select custom fields in GoHighLevel. Any BSI tags that exceed GoHighLevel's tag length or character limits are truncated and documented for the admin to review post-migration.