Migrate from BookingKoala to Salesforce Sales Cloud

Direct map. Every BookingKoala customer becomes a Salesforce Contact. Email uniqueness enforced by Salesforce — duplicates flagged before insert. Multi-location customers with several service addresses store the primary location in BillingAddress; additional addresses migrate as custom address fields on the Contact record.

Direct map with Provider_Role__c custom pick-list to distinguish providers from customers in the shared Contact object. BookingKoala's provider fields (service type, status, rating) migrate as custom fields. Provider email matched to Salesforce User by email for owner assignment on related bookings/opportunities.

BookingKoala bookings become Salesforce Opportunities. Service type maps to Opportunity Name for readability; the original BK booking ID persists in BookingKoala_ID__c for delta-run de-duplication and traceability. Booking status (confirmed, completed, cancelled) maps to a custom Opportunity_Status_BK__c pick-list.

BookingKoala industries (Home Cleaning, Pet Groomer, Moving Service, etc.) migrate as a custom Industry_BK__c pick-list on Opportunity. Multi-industry accounts create separate Opportunity records per industry — your admin decides whether to consolidate or split based on reporting needs.

Invoice__c is a custom object linked to Opportunity via BookingKoala_ID__c lookup. Invoice status (paid, pending, overdue) maps to a custom pick-list. If your BookingKoala setup uses fewer than 500 invoices, we can alternatively store invoice totals and status as Opportunity custom fields to reduce custom object count.

Payment__c is a custom object linked to Invoice__c or Opportunity. Payment method, transaction ID, and payment date migrate as custom fields. Stripe or payment processor references stored in Source_Payment_ID__c for reconciliation if you reconnect a payment integration post-migration.

Review__c is a custom object with a 1–5 star Rating__c (Number), reviewer name, Comment__c (long text), Provider_Response__c, and a lookup to the Opportunity representing the original booking. Salesforce has no native review/rating construct — this custom object preserves your review history for reporting after migration.

Referral__c captures the referring customer and the referred customer's Contact record, credit amount, and referral status. BookingKoala's referral credit logic has no Salesforce equivalent — the custom object preserves the credit history; your admin rebuilds the credit application logic in Salesforce Flow.

BookingKoala email campaigns migrate to Salesforce Campaign records with campaign type, status, scheduled date, and audience count. Campaign member associations (which customers received which campaign) migrate as Campaign Member records. Email templates and automation logic do not migrate — exported as a PDF rebuild reference for your Salesforce admin.

Checklist__c captures job subtasks, completion status, notes, and job media references linked to the Opportunity representing the original booking. BookingKoala's admin and staff checklist subtasks persist as Checklist_Item__c records or as a serialized custom text field depending on the volume of subtask data per booking.

Coupon__c stores coupon code, discount type (percentage vs. fixed), discount value, usage limits, and validity dates. Applied coupons on bookings stored as a lookup on Opportunity. The discount application logic must be rebuilt in Salesforce Flow or CPQ post-migration.

BookingKoala file attachments (job photos, signed forms, receipts) re-upload to Salesforce Files via the ContentDocumentLink model. Files linked to the Opportunity (booking) and Contact (customer/provider) records. Salesforce's 25MB per-file limit applies — files exceeding this are flagged before migration for manual handling.