Migrate from BookingKoala to Pipedrive

BookingKoala Provider records map directly to Pipedrive People. Name, email, phone, and address fields translate field-for-field. Provider status (active/inactive) migrates as a Pipedrive custom field since Pipedrive People have no native active/inactive flag. Providers who are not yet Pipedrive users are flagged for owner assignment before the full run.

BookingKoala Customer records map to Pipedrive People just like Providers. Customer referral credits, block status, and account notes surface as Pipedrive custom fields on the Person record. If a Customer also appears as a Provider in BookingKoala, FlitStack deduplicates by email and preserves both roles as a single Person with a multi-role custom field.

Providers who are also internal staff members in Pipedrive are resolved by email match against Pipedrive Users. When a Provider email matches a Pipedrive user, the Provider record becomes the User's linked Person record. Booking ownership then maps to Pipedrive Deal OwnerId. Providers without a Pipedrive user match land as People without an owning user.

BookingKoala Bookings are the primary record type for migration into Pipedrive Deals. Each booking's total price maps to Pipedrive Deal value. The booking's scheduled date becomes the Pipedrive Deal expected_close_date. Pipedrive stage assignment uses a configurable status mapping: Confirmed bookings → Won stage, Pending → your designated open stage, Cancelled → Lost stage. Bookings with multiple line items (add-on services, upgrades) aggregate into a single Deal value.

BookingKoala time logs and job notes translate to Pipedrive Activities — Tasks for completed service steps, Meetings for scheduled appointments, and Notes for admin commentary. Original timestamps and provider names (activity owners) are preserved. Activity type is inferred from BookingKoala's job_status field.

BookingKoala Industries (Home Cleaning, Pet Groomer, Moving Service, etc.) have no direct Pipedrive equivalent. FlitStack maps Industry to a Pipedrive Organization custom field (Industry_Type__c) or to a Product item if the industry drives repeatable service catalog entries. A separate Organization record is created per Industry when your migration plan requires cross-referencing service categories against Pipedrive Organizations.

BookingKoala Booking Forms capture customer intake data with field types (text, dropdown, checkbox, date). Each form field with a non-trivial structure migrates as a Pipedrive custom field on the linked Person or Deal record. Form logic (conditional display rules) cannot migrate — FlitStack exports form definitions as a JSON spec for your Pipedrive admin to rebuild in Pipedrive's custom field configuration.

BookingKoala service definitions with fixed or parameter-driven pricing map to Pipedrive Products when your migration plan calls for Products-enabled deals. Each service becomes a Product item with a base price, and the Booking Deal pulls the Product into deal_lines. For variable pricing (hourly, parameter-based), the effective booking amount is stored on the Deal and the Product is linked as a reference.

BookingKoala email Campaigns and automated sequences have no direct Pipedrive equivalent. FlitStack exports Campaign definitions (trigger conditions, email content references, timing rules) as a structured document. Your Pipedrive admin can rebuild campaign logic using Pipedrive Automations and the optional Campaigns feature (add-on on higher tiers). Campaign membership (contacts targeted by a campaign) migrates as Activities with a campaign_reference note on each Person.

BookingKoala customer referral credits (balance, credit history) have no Pipedrive equivalent. Migrated as Referral_Credit_Balance__c on the Person record — a numeric custom field for referral tracking. Credit redemption logic must be managed outside Pipedrive or via a custom integration. FlitStack preserves the referral balance as a static numeric value during migration and generates a separate referral transaction log that your team can import into a dedicated referral management system or use to rebuild credit redemption logic in Pipedrive Automations when appropriate.

BookingKoala payment records and card hold status are payment-processing constructs with no Pipedrive equivalent. Payment status is preserved as a Note on the linked Deal with a payment_status label. Full payment history requires BookingKoala records post-migration or a separate accounting tool.

BookingKoala custom properties (text, number, dropdown, checkbox) on Providers, Customers, or Bookings migrate as Pipedrive custom fields on Person or Deal. Pipedrive custom fields require pre-creation per account and use hash-key identifiers. FlitStack generates a custom-field creation manifest before the migration run so fields exist in Pipedrive before data lands.