Migrate from Bridgify to Zoho CRM

Bridgify supplier records (company name, domain, KYC status, commission tier) map directly to Zoho Accounts. We use the Account Name as the primary key and preserve the supplier's Zoho Account Type as 'Partner' or 'Supplier' based on Bridgify's partner classification field.

Partner contact records (name, email, phone, role at supplier) map to Zoho Contacts. Each Contact is linked to its parent Account (the supplier/partner Account record). Primary contacts are flagged via the Is Primary Contact check-box in Zoho. The role title maps to the Contact's Title field for organizational clarity.

Bridgify experience records (name, description, duration, category, destination, supplier) map to Zoho Products by default. If the setup uses experience-specific attributes (difficulty rating, accessibility flags, inclusion details), we create a Zoho Custom module called 'Experience' to hold these fields, with a lookup to the Supplier Account.

Bridgify bookings (customer reference, experience booked, date, total amount, currency, status) become Zoho Deals. The Booking ID is stored as Source_Booking_ID__c. Deal Stage maps from booking status: Confirmed → Closed Won, Pending → 'Negotiation', Cancelled → Closed Lost. Line items in Zoho carry the experience name and quantity.

Each experience unit within a booking (e.g., 2 adults + 1 child for a tour) becomes a Zoho Deal Line Item with quantity, unit price, and product lookup to the corresponding Experience/Product record. Currency is preserved per line item to maintain multi-currency accuracy.

End-user customer records from Bridgify bookings map to Zoho Contacts. Because Bridgify stores customers as booking sub-records, we extract unique customers by email, deduplicate, and create one Zoho Contact per customer. Customer type stored as a custom pick-list (Tourist, Corporate Booker, Loyalty Member).

Bridgify's real-time availability and per-date pricing are live-API data with no static storage. We preserve the last-synced availability snapshot as custom text fields on the Zoho Product record (Last_Synced_Availability__c) and recommend rebuilding live availability via a Zoho webhook or third-party connector.

Bridgify settlement records (gross revenue, commission earned, net payable to supplier, settlement currency, payment status) are stored in a Zoho Custom module called 'Settlement' with lookups to the parent Account and Deal. Settlement Status pick-list maps to Zoho's closing status values.

KYC documents, contracts, and onboarding records stored as attachments in Bridgify are downloaded and re-uploaded to the corresponding Zoho Account record as Files/Attachments. Original filenames and upload timestamps are preserved in the file metadata for audit trail purposes.

Bridgify user accounts (sales rep, partner manager) are matched to Zoho Users by email address. Unmatched users are flagged and assigned to a Zoho fallback user. Ownership on migrated Deals and Accounts is set from the user who created the record in Bridgify.

Bridgify white-label branding settings (logo, subdomain, custom domain) are a platform-level configuration with no direct Zoho CRM equivalent. We document the settings in a Zoho Notes field on the primary Account for reference; DNS and branding setup is a separate technical task.

AI-generated itinerary outputs from Bridgify are stored as unstructured JSON blobs. We extract key itinerary summaries (destinations, dates, activities) and append them as Zoho Notes on the associated Contact or Deal record for reference. Full itinerary reconstruction is not attempted due to format incompatibility.