Migrate from BookingKoala to Twenty CRM

BookingKoala Customer records map directly to Twenty People. Fields including name, email, phone, address, and notes transfer as-is. A BookingKoala customer who has a company association will need the company name mapped to a Company record first, then linked via companyId on the People import. FlitStack sequences the migration so Company records load before People records to resolve the foreign key relationship correctly.

BookingKoala customers optionally carry a company name. When present, this maps to a Twenty Company record using the company name as the displayName. If no company name exists in BookingKoala, no Company record is created — the People record stands alone with no companyId link. Duplicate company names in BookingKoala (multiple customers referencing the same employer) are deduplicated to a single Company record with multiple People records linked to it.

BookingKoala Provider records (name, email, phone, service categories assigned) map to Twenty People records with a custom Provider_Role__c field set to 'Provider' to distinguish them from customer People records. Provider records do not automatically become Twenty Workspace Members — FlitStack flags any BookingKoala provider without a corresponding user email and surfaces them for your team to create Workspace Member accounts in Twenty Settings → Members before the migration runs, so that the provider attribution on booking records can resolve correctly.

Each BookingKoala Booking record becomes a Twenty Opportunity. The Opportunity Name is constructed as '[Customer Name] — [Service Type] — [Scheduled Date]'. The booking amount maps to Opportunity Amount. Booking status (confirmed, completed, in-progress, cancelled) maps to a custom Booking_Status__c pick-list field. The scheduled date maps to the Opportunity's expectedCloseDate custom field. The customer is linked via the People record already imported, and the provider attribution is stored in a custom Provider_ID__c field pointing to the relevant People record.

BookingKoala service types (from the Industry and Service setup) have no native equivalent in Twenty's Opportunity object. We create a custom pick-list field Service_Type__c on the Opportunity object in Twenty before the migration runs. The pick-list values are populated from BookingKoala's service catalog export. If a booking references a service type not in the pick-list, it is imported as a free-text custom field value and flagged for your team to review.

BookingKoala booking status values (Confirmed, In-Progress, Completed, Cancelled, No-Show) map to a custom Booking_Status__c pick-list field on Twenty Opportunities. Each status value is mapped explicitly — Cancelled and No-Show statuses trigger a note on the Opportunity record indicating the original BookingKoala status, since Twenty's native stage model is oriented around sales pipeline progression rather than service delivery states.

BookingKoala Industries represent business categories (Home Cleaning, Pet Grooming, Moving Service) and each Industry has one or more Booking Forms attached. When migrating, we split this concept: the Industry name becomes a custom Industry_Category__c text field on the Company record, and the specific service delivered in each booking is captured in the Service_Type__c field on the Opportunity. This two-level mapping preserves both the vertical category and the specific service without requiring a complex custom object.

BookingKoala pricing can be simple (flat fee) or complex (hourly rate × duration × parameters). The calculated booking amount maps directly to Opportunity Amount. If BookingKoala uses pricing parameters (multiplying base rate by service category, duration, or add-ons), the breakdown is captured as a Note attached to the Opportunity, preserving the pricing logic for reference even though it cannot reproduce BookingKoala's live calculation engine.

BookingKoala Campaigns and automations (email triggers, SMS on booking confirmation, review request sequences) have no equivalent in Twenty CRM's workflow model. Twenty's workflow builder is available on Professional and Organization tiers but does not include native sequencing, CRM-triggered email sends, or SMS actions. FlitStack exports your BookingKoala automation definitions as a JSON reference document listing each workflow name, trigger condition, and action sequence so your team can rebuild them in Twenty or a third-party tool like Zapier.

BookingKoala booking notes (internal staff comments, checklist completions, special instructions) migrate as Twenty Notes attached to the corresponding Opportunity record. If BookingKoala files are attached to a booking (photos, signed documents in My Drive), those are downloaded and re-uploaded as file attachments on the Opportunity or the related People record, subject to file size limits.

BookingKoala payment records (deposit taken, full payment captured, partial payment, refund) have no native equivalent in Twenty CRM — Twenty does not include a payment processing module. Payment and invoice history is preserved as a Note on the Opportunity record with the original payment amount, method, and date captured. For full payment accounting, a custom object can be created in Twenty Professional and Organization tiers to hold payment records, linking to the Opportunity via a relation field.

Any BookingKoala custom property (added via the custom fields feature on Customers, Providers, or Bookings) is assessed for type compatibility. Text, number, date, and select types create matching custom fields in Twenty via Settings → Data Model before the migration runs. Multi-select values from BookingKoala are stored as comma-separated text in Twenty's custom field to preserve the data without requiring multi-select field creation, which Twenty handles differently depending on version.