Migrate from Bridgify to HighLevel

Bridgify Partner Contact records map directly to HighLevel Contacts. Name, email, phone, and address fields carry over 1:1. Owner resolution matches Bridgify user email to HighLevel user email; unmatched owners flag before migration for team assignment. During the mapping, we also preserve the original contact tags and any custom fields that map directly to HighLevel's Contact object.

Bridgify partner or supplier organization records map to HighLevel Companies. Company name, domain, industry, and employee count transfer as direct fields. HighLevel's Company object is a primary entity for Contact-to-Company association — contacts without a mapped company attach to a default placeholder.

Bridgify booking transactions with monetary value map to HighLevel Opportunities. Booking amount becomes Opportunity.Amount, booking close date becomes CloseDate, and booking status maps via value_mapping to a HighLevel Opportunity Stage per pipeline. The Opportunity Name derives from the experience name plus a booking reference suffix.

Bridgify Experience records have no direct HighLevel equivalent — we create a custom object Experience__c with custom fields for Experience_ID__c, Name, Supplier__c, Country__c, Category__c, Duration_minutes__c, Pricing_type__c, Base_price__c, and Availability_status__c. Supplier-specific JSON metadata fields become additional custom fields or a Long Text Area field.

Bridgify Booking records map to a custom object Booking__c with a Contact lookup and optionally an Opportunity lookup. Key fields: Booking_ID__c, Experience__c (lookup), Status__c (pick-list: pending/confirmed/cancelled), Confirmation_code__c, Guest_count__c, Booking_date__c, Total_price__c, Currency__c, Supplier_reference__c. All timestamps are preserved in UTC, and any linked booking notes or internal comments are stored in a Long Text Area field for audit continuity.

Bridgify Order records containing line items and payment status map either to Opportunities (if tied to a revenue-generating deal) or to a custom Order__c object with Order_ID__c, Status__c, Total_amount__c, and line-item fields as a JSON or repeated custom fields. The mapping decision depends on whether the order maps to a pipeline deal or stands alone.

Bridgify has no visual pipeline object — booking status codes (pending, confirmed, cancelled) map to HighLevel Opportunity Stage values via value_mapping. FlitStack creates a Pipeline in HighLevel before migration with stage names that correspond to Bridgify status codes. Probability values and forecast category assignments come from HighLevel's standard stage configuration.

Bridgify supplier-specific custom metadata stored as JSON alongside Experience records translates to individual custom fields on the Experience__c custom object in HighLevel. Fields with a defined set of values become pick-lists; open-ended values become text or long-text fields. Supplier-specific fields that share a schema across suppliers use a consistent field definition.

Bridgify tags on Contact, Company, or Experience records map directly to HighLevel Tags. Tags are a flat string list on each HighLevel record. Tags used to denote supplier categories, experience types, or booking segments carry over without transformation. They can be filtered in HighLevel dashboards and used to trigger workflow actions, providing a simple way to segment data across the migrated dataset.

Files attached to Bridgify Experience or Booking records (e.g., supplier contract PDFs, experience imagery) are downloaded and re-uploaded to HighLevel's Files object, associated to the matching Experience__c or Booking__c record. File size limits follow HighLevel's standard upload constraints. All file metadata, such as original creation dates and author information, is preserved where possible to maintain a complete audit trail.

Bridgify's supplier network data — supplier name, network source, contact info, commission structure — has no HighLevel equivalent. We create a Supplier__c custom object with Name, Network__c (pick-list), Contact_email__c, and Commission_rate__c fields. Experience__c records carry a Supplier__c lookup to link experiences to their source supplier.

Bridgify user accounts (internal team members managing the platform) map to HighLevel Users by email address match. Owner assignment on migrated records uses the matched HighLevel User ID. If a Bridgify user has no HighLevel counterpart, records are assigned to a designated fallback owner and flagged in the migration report.