Migrate from Bizstim Business Management Software to Salesforce Sales Cloud

Biztim Client records map to either Salesforce Lead or Contact depending on the customer's business model. Clients who are active service recipients with a practitioner assignment map to Salesforce Contact attached to an Account; inactive or prospect-stage clients map to Salesforce Lead. We compute the split during scoping using Biztim status fields and practitioner assignment presence. The original Biztim client status and practitioner_id are preserved in custom fields on both Lead and Contact for audit and reconciliation. Address, phone, email, and availability window fields migrate as typed Salesforce fields.

Biztim Practitioner records with system login credentials map to Salesforce User records for scheduling and assignment data. Practitioners who are non-user staff (external coaches, freelance tutors) map to Salesforce Contact records with a custom practitioner_type__c field. practitioner_wage settings map to a custom wage field on User or Contact. We deduplicate Practitioners against Staff records (staff_id and practitioner_id are the same entity in Biztim) before migration and build a routing matrix during scoping to determine which Practitioners become Users versus Contacts.

Biztim Service records map to Salesforce Product2. The service cost maps to UnitPrice in the Standard Pricebook. session count stored in group_num maps to a custom field sessions_per_package__c. Biztim's service group_id defines which services belong to a bundle; we preserve this as a custom bundle_id__c field on Product2 and create a written bundle mapping guide so the customer's admin can configure Product Bundles or Salesforce CPQ if they use it.

Biztim service_group_names table entries define parent-child bundle relationships via group_id. We extract the full group hierarchy and preserve it as a custom bundle_id__c reference field on each Product2. Bundle pricing and the ordering of services within a bundle require manual configuration in Salesforce by the customer's admin using Product Bundles (requires CPQ) or a custom Visualforce page. We deliver a written bundle inventory document mapping every group_id to its constituent service records.

Biztim Payment records (amount, date, client association) map to Salesforce Opportunity if the customer tracks revenue by service delivery; they map to a custom Invoice__c object if the customer uses Salesforce primarily for CRM tracking without pipeline management. We resolve the client-to-Contact/Lead mapping and the practitioner-to-User/Contact mapping before inserting payment records so that WhoId and WhatId references are satisfied. Currency fields migrate as-is; multi-currency orgs require currency ISO codes to be validated before insertion.

Biztim Client records contain minTime, maxTime, slotDuration, and sessionLimit fields defining individual availability windows. We extract these as structured availability rules and deliver them as a written configuration guide for Salesforce Scheduler (available in Lightning Experience with Enterprise+ licenses) or as records in a custom Availability__c object that the customer's admin maps to their chosen scheduling tool. Availability data does not map to a native Salesforce standard object.

Biztim Users endpoint returns login information and role data. We export user records to identify owner and assignee mappings in the destination Salesforce org. Email is the dedupe key. Biztim role values (admin, practitioner, staff) map to Salesforce Profile and Permission Set assignments that we document for the customer's admin to configure before production migration.

Biztim Staff records are distinct from Practitioners but share the same underlying staff_id. We consolidate Staff and Practitioners during extraction, deduplicating by staff_id. Staff who require Salesforce login access (admins, managers) map to User; support and operations staff without login requirements map to Contact with a staff_type__c custom field.

Biztim free-text notes on Client records migrate to Salesforce Note objects linked via ContentDocumentLink to the parent Contact or Lead record. Rich text formatting in Biztim notes is preserved as HTML in the Note Body field. Note timestamp migrates as the ActivityDate on the Salesforce Note so that note ordering in the timeline is preserved.

Biztim On-Demand encrypted links generate session access URLs tied to custom student identifiers and agent IDs. These are temporary session-scoped tokens that expire and are not portable across systems. We identify and count these records during scoping for completeness of the data audit, but they are not inserted into Salesforce. We document the count and the business context so the customer knows what session-link functionality is not reproduced.

Binary file attachments stored within Biztim client records must be identified separately during the scoping call because the Biztim API does not expose attachment download URLs through the standard REST endpoints. We flag any attachment records found in the client export, report their file types and sizes, and provide a manual download checklist for the customer's admin. Attachments that are reachable via a separate Biztim file API are migrated as Salesforce ContentDocument records with ContentVersion.

Practitioner wage settings from Biztim (practitioner_wage fields) migrate to custom fields on the Salesforce User record (for staff practitioners who get Salesforce login) or to custom fields on Contact (for non-user practitioners). We resolve the practitioner_id reference during User and Contact import so that the wage data attaches to the correct record. Any practitioner without a resolved user or contact destination is held in a reconciliation queue for the customer's admin to resolve before the final migration phase.