Migrate from Bridgify to Salesforce Sales Cloud

Booking-to-Opportunity mapping requires a schema decision before migration

Bridgify Bookings are transactional records with a clear lifecycle (created, confirmed, cancelled, refunded) that does not map 1:1 to Salesforce's Opportunity model. If your team uses Salesforce for booking pipeline tracking—status, probability, forecast—then Booking maps to Opportunity with custom stage values. If bookings are purely transactional and your sales team tracks the relationship separately, a custom Booking__c object with a status pick-list is more appropriate. Making the wrong call before migration causes re-work. We surface the decision during the schema-planning step and document it in the field-level mapping plan before any data moves.

Real-time availability fields on Experiences have no native Salesforce equivalent

Bridgify Experiences store real-time availability slots, dynamic pricing, and supplier inventory status. Salesforce has no native availability model—Product2 + PricebookEntry handle static pricing, not slot-based availability. We migrate historical availability snapshots as custom fields on the Experience__c object, but live availability must be rebuilt using Salesforce CPQ, a custom app, or an AppExchange availability solution. This is a post-migration configuration item, not a data loss issue, but it requires planning before go-live.

Multi-currency settlement requires DatedExchangeRate pre-loading

Bridgify tracks multi-currency settlements across 180+ countries. Salesforce's Advanced Currency Management uses DatedExchangeRate to handle historical exchange rates, but these rates must be loaded before settlement records migrate. If Bridgify settlement amounts are stored in original currency and converted amounts, both the original currency and the converted amount must map to separate fields. Currency conversion is not performed by FlitStack—rates must be sourced and loaded by your finance team before migration.

Supplier hierarchy depth causes recursive migration ordering

Bridgify supplier hierarchies can nest multiple levels deep (parent supplier → regional supplier → local operator). Salesforce ParentId on Account is a single-level parent reference, not a recursive tree. We migrate the deepest child first, then its immediate parent, working upward. Circular references—where two suppliers reference each other as parents—are flagged as migration errors and must be resolved manually before migration. Flat hierarchies migrate cleanly; deeply nested hierarchies require a custom junction-object strategy.

White-label configuration fields are not translated to Salesforce equivalents

Bridgify's white-label marketplace stores brand configuration (logo, colors, subdomain, custom domain) per partner. Salesforce has no white-label storefront capability at the CRM level—Experience Cloud would be required for partner-facing portals. We preserve white-label config JSON as a long-text field on the Partner Account for reference, but the portal itself must be rebuilt in Experience Cloud post-migration. This is not a data loss issue; it is a separate implementation project. We recommend documenting the current white‑label settings in a configuration matrix so the Experience Cloud build can reference the original values accurately.