Migrate from BookingKoala to Odoo CRM

BookingKoala customer records map directly to Odoo res.partner. Customer name, email, phone, address, and created date transfer as res.partner fields. Primary company association uses parent_id if customer represents a business account. All contact details are validated against Odoo's data integrity rules, and duplicate detection is performed using email as the unique key to prevent redundant partner records.

BookingKoala providers (field workers) map to res.partner with a custom provider_flag__c boolean field. If Odoo HR module is active, providers can alternatively map to hr.employee. Availability schedule and provider notes transfer as custom fields. The provider_flag__c field enables quick filtering of contacts by their worker role, and any existing availability windows are stored as a serialized JSON string for Odoo scheduling modules.

BookingKoala booking records are the primary migration unit translated into Odoo crm.lead (opportunity) records. The booking service type becomes a custom field, booking status maps to crm.stage progression, and customer link uses partner_id on crm.lead. Additional metadata such as booking source, internal notes, and custom pricing tiers are preserved in dedicated fields to maintain full context for sales and support teams.

Individual service lines within a BookingKoala booking (e.g., deep clean, move-out clean) map to a custom One2many field on crm.lead representing service_items__c. Each line captures service_name, quantity, unit_price, and duration. This structure supports detailed revenue breakdown, allows Odoo reporting on per-service performance, and enables accurate invoicing by linking each line to the corresponding account.move.line record.

BookingKoala industries (Home Cleaning, Pet Groomer, Moving Service, etc.) map to Odoo crm.team records — one team per industry. Alternatively, a custom industry_tag__c pick-list field on crm.lead stores the industry value when teams aren't needed. During migration, we create the crm.team records first, then assign the appropriate team_id to each crm.lead based on the source industry, ensuring proper pipeline segmentation in Odoo.

BookingKoala invoices migrate as draft account.move records in Odoo Accounting. Invoice lines map to account.move.line_ids, customer maps to partner_id, and payment_state stays 'draft' until validated in Odoo. Tips and taxes preserved as line notes. We flag any invoice that references a non-standard tax rate for manual review, and we provide a reconciliation checklist to guide your accountant through the validation steps.

BookingKoala payment transactions map to Odoo account.payment records linked to the migrated invoice (account.move). Payment method, amount, date, and transaction reference transfer. Stripe/payment gateway references stored as payment_reference. Each account.payment record also inherits the partner_id from the associated account.move, ensuring that Odoo's payment reconciliation engine can automatically match incoming payments to open invoices.

BookingKoala booking statuses (Pending, Confirmed, In Progress, Completed, Cancelled) map to Odoo crm.stage records via value mapping. Stage sequence order follows BookingKoala's workflow progression. Probability weights assigned per stage. The probability values align with typical sales cycle expectations, allowing Odoo's forecasting tools to generate realistic revenue projections based on the migrated booking pipeline.

BookingKoala referral credits per customer map to a custom referral_credit__c decimal field on res.partner. Referral history stored as a serialized note field. Credit redemption rules require Odoo loyalty program setup post-migration. We also provide a mapping template for loyalty points conversion, ensuring that existing referral balances translate accurately into Odoo's loyalty currency without loss of value.

BookingKoala customer ratings and reviews migrate as mail.message records attached to the crm.lead or res.partner. Rating score stored as a custom rating_score__c integer field. Review text preserved in message body. These messages appear in Odoo's chatter, giving sales and support staff immediate visibility into past customer feedback and enabling follow-up actions directly within the CRM record.

BookingKoala admin and staff accounts have no Odoo CRM equivalent. Owner resolution uses email matching against Odoo res.users. BookingKoala staff without Odoo accounts receive a fallback owner flag for reassignment post-migration. We also generate a reconciliation report listing each matched and unmatched user, along with recommended Odoo user roles, to help your admin complete the access configuration quickly.

BookingKoala booking checklists (admin/staff task lists) map to project.task if Odoo Project module is active. Otherwise, checklist completion status migrates as serialized JSON in a custom checklist_data__c field on crm.lead. When the Project module is used, each checklist item becomes a sub-task linked to the crm.lead, allowing project managers to track task progress directly within Odoo's project board.