Migrate from Bridgify to Pipedrive

Each Bridgify booking becomes a Pipedrive Deal. The booking reference number is stored in a custom Pipedrive field (cf_booking_reference) for traceability back to Bridgify. The experience date maps to the deal's close_date so Pipedrive's stage-at-risk reporting reflects upcoming experience dates.

Bridgify stores customer name, email, and phone as properties of the booking record. We extract these into standalone Pipedrive Person records. For repeat customers (multiple bookings), we de-duplicate by email match so one Person record accumulates all deal history in Pipedrive.

The tour operator, activity provider, or experience supplier stored in a booking maps to a Pipedrive Organization. Supplier contact details (if available) become Organization custom fields. If the same supplier appears across multiple bookings, we collapse to one Organization linked to all related deals.

The specific tour, activity, or experience type (e.g., 'Full-Day City Tour', 'Cooking Class') migrates as a Pipedrive Product with standard price. Deals are optionally linked to Products if your Bridgify setup records which experience was booked per transaction. This mapping enables Pipedrive reporting on revenue by experience type and maintains a product catalog that travel teams can reference when creating deals for repeat customers.

Bridgify booking statuses map to Pipedrive stage values: 'Confirmed' → Open stage, 'Completed' → Won stage, 'Cancelled' → Lost stage. We preserve original status labels in a custom field (cf_booking_status_original) so you can report on historical status distributions in Pipedrive's list views.

The total booking revenue (in source currency) migrates directly as Pipedrive deal value. If multi-currency amounts are stored, we preserve the numeric value and store the original currency code in a custom field (cf_currency_code) since Pipedrive stores deal value as a single decimal field.

Bridgify booking event records (confirmation sent, supplier confirmed, payment received, customer contacted) migrate as Pipedrive Tasks. Each task inherits the booking's creation timestamp as the Pipedrive Activity timestamp and the deal ID as the parent link. We attach these to the target Deal so the full event history is visible in Pipedrive's activity feed.

Bridgify custom booking properties that have no direct Pipedrive equivalent become custom fields. We pre-create the Pipedrive field (via POST /dealFields or /personFields API) using the field's label as the display name, then write values during migration. Pipedrive assigns a 40-character hash key to each field — we handle the key assignment automatically.

Loyalty tier values (Gold, Silver, Bronze or VIP, Regular, New) stored against a customer profile in Bridgify migrate as a custom pick-list field on the Pipedrive Person. We preserve the exact tier label from Bridgify and store it as a Person-level custom field (cf_loyalty_tier) for segmentation in Pipedrive lists and automations.

Bridgify notes attached to a booking (special requests, dietary requirements, accessibility needs) migrate as Pipedrive Notes linked to the corresponding Deal. We preserve the original author and timestamp. Notes with @mentions to suppliers are stored as plain text since Pipedrive Notes do not support @mention resolution.

Booking-triggered rules in Bridgify (e.g., send confirmation email on booking creation, notify supplier on status change, update payment field on receipt) have no equivalent in Pipedrive's migration scope. We export your rule definitions as a structured JSON file so your Pipedrive admin can rebuild equivalent automations using Pipedrive's Automation builder.

If Bridgify stores negotiated supplier rates or contract terms as properties of the supplier record, we migrate these as Organization-level custom fields in Pipedrive (cf_supplier_rate, cf_contract_expiry). The source field values are preserved verbatim; Pipedrive's reporting does not natively calculate from these without a custom formula field.