Migrate from Sharp CRM to HighLevel

Sharp CRM Contact records map to GoHighLevel Contact records. Standard fields (first name, last name, email, phone, address) map directly. We run deduplication by email before import to avoid creating duplicate records. Custom fields on the Sharp CRM contact record are enumerated during scoping, classified by data type (text, number, date, dropdown, checkbox), and mapped to GoHighLevel Contact custom fields. Any custom fields without a clear GoHighLevel equivalent are flagged for the customer to decide before import.

Sharp CRM Companies map to GoHighLevel Contact records where the contact_type field is set to Company. We import Companies first, then import Contacts with their associated company relationship resolved via the company_name or domain field. In GoHighLevel, organization-level data lives on a Contact record rather than a separate object, so company address, website, and industry fields are mapped to the corresponding Contact custom fields on the company-type Contact record.

Sharp CRM Deals map to GoHighLevel Opportunities. Deal name, value, close date, and stage migrate directly. Pipeline stage names from Sharp CRM (which are unique per account) must be mapped to the GoHighLevel pipeline stages that we configure before migration. If Sharp CRM has multiple deal pipelines, we create corresponding GoHighLevel pipelines and assign the correct pipeline to each Opportunity record during import.

Sharp CRM pipeline stage definitions do not export in standard format. We ask the customer to provide their current stage names and order during scoping and build an explicit stage-mapping table. Each mapped stage is created in GoHighLevel as a pipeline stage before Deal import, with the stage probability populated from the Sharp CRM stage data if available. Stage order and visual placement in the GoHighLevel pipeline view are configured to match the source workflow.

Sharp CRM Tasks migrate to GoHighLevel Tasks. Title, due date, assignee (resolved by email to GoHighLevel User), priority, and completion status migrate directly. Tasks without an assignee are assigned to the GoHighLevel account owner during migration. Task notes or descriptions migrate as task body content.

Sharp CRM Activity records (calls, emails, notes) migrate to GoHighLevel Activity Log entries attached to the parent Contact. Activity type, timestamp, and body content migrate as plain text. Call duration and disposition migrate to GoHighLevel call custom fields if configured; otherwise they are preserved in the activity notes. Email subject and body migrate to the note content field on the activity log entry.

Sharp CRM custom fields are enumerated per customer during scoping, classified by data type and target object (Contact vs. Opportunity). GoHighLevel requires custom fields to be created in the platform before import, so we create the fields first in GoHighLevel using matching data types (text, number, currency, date, dropdown, checkbox), organize them into folders per the customer's Sharp CRM field groups, and then map the Sharp CRM field values during import. Any fields without a GoHighLevel equivalent are flagged for the customer to resolve.

Sharp CRM tags on Contacts and Deals migrate to GoHighLevel Tags. Tags are stored as arrays in Sharp CRM and are mapped to GoHighLevel's tagging system. If the customer uses tags for segmentation or workflow triggers, we document the tag usage during scoping so that the customer can recreate the segmentation logic in GoHighLevel's Smart List or workflow conditions after migration.

File attachments associated with Sharp CRM Contacts or Deals are exported to a file store with record ID metadata. We link each file to the corresponding Contact or Opportunity record in GoHighLevel by uploading to the contact record's file section. Large attachments are linked with the migration file store URL in a custom field so the file remains accessible if the link breaks.

Sharp CRM User records (name, email, role) migrate to GoHighLevel User accounts. We match users by email address. Active status migrates as-is; inactive users are provisioned as inactive GoHighLevel users so that historical assignee data remains intact. Seat counts and role permissions are re-evaluated post-migration based on the customer's GoHighLevel plan tier.