Migrate from Bridgify to HubSpot

Bridgify contact fields (name, email, phone, jobtitle, address) map directly to HubSpot contact properties. HubSpot contact records are created for each unique email in Bridgify. Duplicate emails are merged; original timestamps preserved as Original_Create_Date__c.

Bridgify booking records that include company name and domain extract to HubSpot company records. Companies are created before contacts so the contact-to-company association resolves via email domain match or explicit company_id field in the source data.

Each Bridgify booking with an amount and currency code becomes a HubSpot deal. The deal name uses the booking ID or a constructed label. Amount maps to the deal Amount property; currency code becomes a custom Deal_Currency__c property. Close date is derived from the booking timestamp or a specified booking close field.

Bridgify's N:N bookings-contacts junction maps to HubSpot's native deal-contact association. When a deal has multiple contacts, all are associated via the standard deal-contact link. A custom Booking_Contact_Role__c property on the contact record captures any role label from the source junction.

Bridgify's company_id on a booking translates to HubSpot's primary company association on the contact record. If the source has multiple company associations per contact, secondary companies are added via HubSpot's secondary company associations feature.

HubSpot has no native loyalty tier concept. FlitStack creates a custom contact property (Loyalty_Tier__c) as an enumeration matching the source tier values (Bronze, Silver, Gold, Platinum, etc.). Tier-upgrade timestamps from the source map to custom datetime fields.

HubSpot does not have a native loyalty points field. FlitStack creates a custom number property (Loyalty_Points_Balance__c) on the contact record, populated from the source balance at migration time. Point transaction history requires a separate custom object if granular history must be preserved.

Enrollment date, program ID, and loyalty program name from Bridgify map to custom contact properties (Loyalty_Enrollment_Date__c, Loyalty_Program_ID__c, Loyalty_Program_Name__c). Each is typed according to source field type (date, string, string). FlitStack validates that source date formats convert correctly to HubSpot datetime and that string values fit within HubSpot property character limits.

Bridgify booking IDs are collected into a custom contact property (Booking_History__c) as a pipe-delimited string or via a HubSpot custom object for bookings, linked by a contact identifier. The approach depends on the volume and whether querying by booking ID in HubSpot is required post-migration.

Bridgify's internal record ID for each contact is stored as Source_System_ID__c on the HubSpot contact. This enables delta-run de-duplication and traceability back to the original Bridgify record for reconciliation purposes.

Bridgify booking amount maps to the HubSpot deal Amount field. The currency code from the source (e.g., USD, EUR, GBP) is stored as a custom string property (Deal_Currency__c) on the deal. Multi-currency conversion is not performed; the original amount and currency are preserved for destination-side reporting.

HubSpot deals have a standard create date (set at migration time). Original Bridgify booking creation timestamps and booking modification timestamps are preserved as custom datetime fields (Original_Booking_Create_Date__c, Original_Booking_Modified_Date__c) for historical continuity in reports.