Migrate from BookingKoala to Nutshell

BookingKoala provider model doesn't map to Nutshell Users

BookingKoala's provider concept (field staff who perform services) has no direct Nutshell equivalent. Nutshell's User model is designed for sales reps with CRM seats, not field service providers. We recommend mapping providers to Nutshell People with a custom Provider_Role__c field to preserve staff identity without requiring additional paid seats. If your providers handle sales follow-ups in Nutshell, Nutshell User seats can be added separately—this is a business decision, not a technical limitation.

Real-time scheduling and calendar sync has no Nutshell equivalent

BookingKoala's real-time calendar synchronization with double-booking prevention is a core platform feature with no Nutshell CRM equivalent. Nutshell uses task-based scheduling linked to Deals, which operates fundamentally differently from appointment scheduling—there's no automatic conflict detection or resource availability checking. BookingKoala booking times and provider assignments migrate as custom fields on Tasks, but the intelligent scheduling engine with availability optimization requires rebuild within BookingKoala (if retained) or migration to a dedicated scheduling tool. This is a fundamental architectural difference between booking and CRM platforms that affects operational workflows.

Complex pricing parameters don't transfer as structured data

BookingKoala's variable pricing setup—category-based rates, pricing parameter dependencies, minimum time/price limits, and volume discounts—uses a configuration model that doesn't map cleanly to Nutshell's product and quote structure. We export pricing as text fields or store key pricing variables as custom Number fields on Deals, but complex pricing logic with conditional rules requires manual rebuild within Nutshell Products and Quote Line Items. During discovery, we document your current pricing rules and dependencies so your Nutshell admin can configure equivalents. Complex multi-tier pricing may require Nutshell's advanced product configuration features or custom development.

Customer reviews and ratings require custom field configuration

BookingKoala's review and rating system is platform-specific with no standard Nutshell equivalent. Star ratings have no built-in CRM field type in Nutshell's native data model. We create a custom numeric field (Customer_Rating__c) on the Person object and migrate review text as Notes attached to the customer record. If your operations depend heavily on rating data for provider performance tracking or customer satisfaction monitoring, this requires custom reporting configuration in Nutshell using the migrated custom fields. The full review content transfers, but rating-based automation or segmentation logic is not an automatic translation and requires post-migration setup.

Multi-location configurations collapse to text fields

BookingKoala supports multi-location businesses with different service areas per provider, customer, or booking type. Nutshell's address model is tied to individual records (People or Companies) rather than supporting a flexible location hierarchy with nested service areas. We store multi-location data as a custom Locations__c text field using comma-separated values or a structured JSON format. This preserves the data but doesn't enable native location-based filtering in Nutshell's standard reporting. Filtering and reporting by location requires custom Views, saved filters, or exports—it's not a native Nutshell reporting dimension and may require additional configuration effort.