Migrate from Bizstim Business Management Software to Nutshell

Biztim Client records map to Nutshell Person objects. The Client email, phone, address, and status fields map directly to Nutshell Person fields. Client availability rules (minTime, maxTime, slotDuration, sessionLimit) are extracted as structured availability data and written to a custom field migration_availability__c on the Person record since Nutshell does not expose a native practitioner scheduling or client availability object. Any binary attachments or file uploads stored within client records are identified during scoping and migrated as separate note attachments.

Biztim Practitioner records map to Nutshell User accounts. The practitioner_id, practitioner name, contact details, and assignment preferences migrate directly. Practitioner payment rates (practitioner_wage fields) have no native Nutshell equivalent and are stored in a custom field practitioner_wage__c on the User record. The Staff object in Biztim is a parallel record set to Practitioner; we consolidate Staff and Practitioner as a single migration object, deduplicating by staff_id and keeping the merged record set.

Biztim Service records map to Nutshell Product entries. The service name, cost, session count (group_num), and practitioner wage defaults transfer to the Nutshell Product name, unit price, quantity, and a custom field practitioner_wage_default__c. Service group hierarchy (group_id linking services to service_group_names) is preserved by writing a custom field service_group__c on each Product so that bundled service packages retain their structural relationship. The Services GET endpoint returns a maximum of 100 records per page; we paginate through all pages, tracking the total count from response metadata.

Biztim Payment records (amount, date, currency, client association via practitioner_id) map to a structured invoice record in Nutshell. Nutshell does not have a native billing or invoicing object in its standard CRM tiers, so we write payment data as a custom object (migration_payment__c) or as structured notes on the related Person record, depending on the customer's Nutshell tier. Currency fields transfer as-is; no currency conversion is performed.

Client records in Biztim carry minTime, maxTime, slotDuration, and sessionLimit fields that define individual availability windows. These availability rules have no direct Nutshell equivalent. We extract them as structured key-value data and write to a custom field migration_availability__c on the Person record during migration. The customer's admin recreates these as manual availability notes or integrates a dedicated scheduling tool post-migration.

Biztim stores practitioner payment rates as practitioner_wage fields on the Practitioner record. Nutshell has no native practitioner wage object. We map these values to a custom field practitioner_wage__c on the Nutshell User record during migration. This is a manual-designated custom field that the customer provisions in their Nutshell workspace before the production migration phase.

Biztim free-text notes and comments stored within Client records migrate as Nutshell Note records linked to the Person object. Binary file attachments or uploaded documents referenced within client records must be identified during scoping because the Biztim API does not expose file storage endpoints. If files are referenced in the note body via URL, we preserve the link in the Nutshell Note; if the files are binary blobs, we flag them for manual extraction and re-upload.

Biztim service_group_names table entries link services to their bundle groups via group_id. We preserve these group definitions as a custom field service_group__c on each Nutshell Product record. This allows the customer's admin to identify bundled service packages and recreate them as grouped or kit-style offerings in Nutshell after migration.