Migrate from Bright to HighLevel

Bright contacts migrate as HighLevel contacts with all standard fields (name, email, phone, address) mapped directly. Owner resolution happens by email match against HighLevel users — unmatched owners are flagged for fallback assignment before migration commits. We also preserve the original contact creation timestamp as a custom field to maintain historical context after migration.

Bright companies map to HighLevel companies. Website, industry, employee count, and annual revenue transfer as direct field maps. Multi-company contacts in Bright (N:N model) collapse to one primary company per contact in HighLevel, with secondary companies surfaced as contact tags.

Bright deals migrate as HighLevel opportunities. The deal name, amount, close date, and owner map directly. Pipeline and stage names are stored as custom fields in HighLevel because HighLevel scopes stage values to pipeline-specific pick-lists rather than flat stage names.

Bright pipelines must be recreated in HighLevel before migration data lands. We deliver a pipeline setup plan based on your Bright pipeline count and stage names so your HighLevel pipeline structure is ready before the first record imports. The plan includes stage probability weights and optional automation triggers for each stage, aligning deal scoring with your sales process.

Bright lifecycle stages have no native HighLevel equivalent. We create a custom pick-list field on the Contact object in HighLevel preserving the exact stage values from Bright. Stage-transition timestamps are preserved in a secondary custom datetime field if your Bright data includes them.

Bright tags migrate as HighLevel tags — all tag associations per contact transfer directly. HighLevel's tag-based workflow triggers and dynamic list filtering work immediately after migration using the migrated tag taxonomy. Tag deduplication runs automatically during migration if your Bright setup accumulated redundant tags.

Bright engagement activities (calls, emails, meetings, notes) migrate as HighLevel tasks and calendar events. Original timestamps, subject lines, and owner assignments are preserved. HighLevel does not have a native activity-timeline view — activities appear in the contact's history section. You can filter tasks by type or date in the contact record to recreate a timeline-like view manually.

Bright notes migrate as HighLevel notes with body content and create timestamps intact. File attachments are re-uploaded to HighLevel's file storage and linked to the associated contact or company record. During re-upload, we retain original file names and maintain the folder hierarchy if one existed in Bright, simplifying navigation in HighLevel.

Bright custom fields map to HighLevel custom fields using type-aware mapping: text to text, pick-list to dropdown, number to number, date to date. Complex Bright field types (formula fields, roll-up summaries) have no HighLevel equivalent — those values are calculated post-migration or stored as read-only reference fields.

Bright workflows and automations do not migrate — the logic constructs are incompatible between platforms. We export your Bright workflow definitions as a reference document you can hand to your HighLevel admin for manual rebuild in HighLevel's workflow builder.

Bright users are resolved by email match to HighLevel user accounts. Users who exist in Bright but have no HighLevel account are flagged before migration so your team can invite them first. Ownership of migrated records is assigned at import time based on the resolved match.