Migrate from Bridgify to Microsoft Dynamics 365 Sales

Bridgify locations (destinations, venues, tour operators) map to Dynamics 365 Accounts with a dedicated Location record type. Address fields map to address1_line1, address1_city, address1_country. Source location ID stored as new_BridgifyLocationId for traceability and delta-run matching. This lookup field enables the migration process to identify and reconcile location records between systems without duplicating existing entries.

Bridgify experiences (tours, activities, attractions) have no direct CRM equivalent. We create a new_BridgifyExperience custom Dataverse table with columns for experience name, category, supplier reference, and pricing tier. A lookup relationship to the parent Account (location) is established using the location ID from Bridgify.

Booking transactions map to Opportunities when the booking value represents a sales opportunity with stage progression (Inquiry → Confirmed → Completed → Revenue). Bookings with fixed pricing and supplier fees map to new_BridgifyBooking custom table with fields for net_amount, supplier_fee, currency_code, and booking_status. The choice depends on whether your team tracks bookings as opportunities in a pipeline or as completed transactions against an account.

Bridgify consumer profiles (name, email, phone, booking history) map to Dynamics 365 Contacts. Email maps to emailaddress1, phone to telephonenumber1, full name to fullname. The primary location (if the consumer has a preferred destination) is stored as new_PreferredLocation lookup. Booking history is preserved as a related sub-grid via the custom booking entity.

B2B partners in Bridgify (OTAs, banks, loyalty programs, super-apps) map to Accounts with a Partner record type. This allows distinct page layouts and pick-list values for partner-specific fields. The partner's API credentials and contract tier are preserved in custom fields new_PartnerTier and new_APIKeyReference — credentials are stored as encrypted notes, not plain text.

Bridgify booking statuses (Pending, Confirmed, Cancelled, Completed, Refunded) map to Opportunity statecode and statuscode combinations. Confirmed maps to statecode=0 (Open), Completed maps to statecode=1 (Won), Cancelled or Refunded maps to statecode=2 (Lost) with corresponding statuscode values. This preserves the booking lifecycle in Dynamics pipeline reporting.

Bridgify suppliers (experiences providers) map to Accounts with a Supplier record type. The supplier's Bridgify supplier ID is stored as new_SupplierId. A relationship between the new_BridgifyExperience custom table and the Supplier Account is established via the lookups defined during schema setup.

Bridgify multi-currency booking amounts map to Dynamics 365's TransactionCurrency entity (ISO currency codes). The booking amount in source currency is stored in custom fields on the Opportunity or new_BridgifyBooking record. Dynamics 365's built-in currency conversion applies the exchange rate from the TransactionCurrency table at the time of record creation.

Bridgify internal user accounts are mapped to Dynamics 365 SystemUser records by email match. Owner assignments on migrated records reference the matched SystemUser ID. Unmatched users are flagged before migration — your Dynamics admin either invites them or assigns records to a fallback owner to avoid orphaned records.

Bridgify booking notes and supplier confirmations migrate as Dynamics 365 Annotations on the parent Opportunity or custom booking record. Original timestamps and note authors are preserved. File attachments from Bridgify are re-uploaded to Dynamics 365's SharePoint-integrated document storage if your tenant has SharePoint integration enabled.

Bridgify's supplier API keys, webhook configurations, and real-time availability polling settings have no Dynamics 365 equivalent. These must be rebuilt post-migration using Power Automate connectors, Azure Logic Apps, or custom Dataverse plug-ins that call the supplier APIs directly. FlitStack exports the Bridgify API configuration as a JSON reference document for your integration team.

Contract terms, SLA tiers, and commission rates from Bridgify supplier agreements are migrated as a custom new_SupplierContract entity with fields for contract_start_date, contract_end_date, commission_rate, and SLA_tier. This entity links to the Supplier Account and provides audit history for compliance-heavy industries like financial services and loyalty programs.