Migrate from Bridgify to Freshsales

Freshsales API rate limits constrain migration throughput on Growth plan

Freshsales applies tiered API rate limits: Growth plan allows 1,000 requests per hour, Pro allows 2,000 per hour, and Estate/Forest allow 5,000 per hour. For large Bridgify datasets (50,000+ bookings), migrations on Growth plan require multiple sessions spread across hours to avoid 429 (Too Many Requests) errors. We implement exponential backoff and request pacing based on your Freshsales plan tier, but plan selection should be made before migration scoping if large record volumes are expected. API rate limits are account-level — they apply regardless of how many Freshsales users your team has. If the Growth plan rate cap is constraining the migration timeline, upgrading to Pro or Estate unlocks higher throughput immediately.

Multi-currency booking amounts require pre-migration normalization

Bridgify handles multi-currency settlement across 180+ countries, storing booking amounts in the original transaction currency. Freshsales Opportunity Amount is a single base-currency numeric field with optional multi-currency enabled at Estate/Forest plan tiers. Bookings in non-base currencies cannot map directly to the Amount field without currency normalization. We flag all non-base-currency bookings before migration, store the original currency in a custom field, and populate Amount with a converted value using the exchange rate at migration time. If your team needs live multi-currency reporting, enable Freshsales multi-currency configuration before migration — we cannot retroactively convert amounts after the migration commits.

Multi-supplier bookings need junction-field strategy before migration

Some Bridgify bookings aggregate experiences from multiple supplier networks — for example, a single booking covering a hotel transfer, a guided tour, and a restaurant reservation with three different suppliers. Freshsales Opportunity has a single AccountId lookup, which supports one primary supplier. Secondary suppliers require either a custom multi-select text field (simplest) or a custom junction object (full relational fidelity). We surface the multi-supplier frequency in your Bridgify data during discovery and recommend the approach before migration runs. Skipping this step means secondary supplier data is stored only in notes, which is harder to report on in Freshsales.

Custom fields must be created in Freshsales before migration runs

Experience metadata fields (duration, category, rating, supplier network, cancellation policy) have no native Freshsales equivalents — they must be created as custom fields on the Opportunity object before any data can populate them. Freshsales custom field creation requires admin access and is subject to your plan tier: Growth and Pro support standard custom fields; advanced field types (lookup relationships, formula fields) require Estate or Forest. We deliver a custom field creation plan as part of the migration setup phase, and we recommend creating and testing all custom fields in a Freshsales sandbox or trial environment before the full migration. Fields created mid-migration require a re-run of affected records.

Bridgify workflows and automations do not migrate and have no Freshsales equivalent

Any booking-triggered automations in Bridgify — such as confirmation emails sent when a booking status changes, supplier routing rules, or availability-triggered pricing updates — are partner-level integrations that do not export as configuration data. Freshsales workflows, sequences, and Journey Builder operate on CRM events (Lead created, Opportunity stage changed, email opened), not on external booking events. The automation logic must be rebuilt in Freshsales using Freshsales Workflows (available on Pro and above) or the Freshsales REST API. We export the Bridgify configuration JSON as a rebuild reference, but the automation itself cannot be transferred automatically.