Migrate from Bizstim Business Management Software to HighLevel

Bizstim client records map directly to GoHighLevel Contacts. The client's email, phone, address, and status fields translate to standard GoHighLevel Contact fields. We preserve any custom free-text fields as GoHighLevel custom fields scoped to the Contact object. Client availability windows (minTime, maxTime, slotDuration, sessionLimit) migrate as appointment type preferences stored in a custom field or linked availability record in GoHighLevel's calendar module.

Bizstim Practitioner records map to GoHighLevel Contacts with a practitioner_role custom field set to Practitioner. Practitioner wage settings (practitioner_wage) migrate as a compensation-related custom field on the Contact. We deduplicate against the Staff object during extraction (Bizstim stores practitioner data in both Practitioners and Staff endpoints) and import once. Team member status in GoHighLevel's Team settings is configured for each practitioner Contact post-import.

Bizstim individual services map to GoHighLevel Products if the destination uses a product-driven quoting model, or to custom Opportunity fields (service_name, service_cost, group_num for session count) if the business uses pipeline Deals without formal products. We determine the strategy during scoping based on whether the customer quotes service packages or tracks them as session-based line items against Opportunities.

Bizstim Service Groups (group_id linking multiple services into a package) translate to GoHighLevel Product Bundles or a custom multi-select field on the Opportunity capturing the constituent service IDs. The group_name becomes the bundle name and group_num (session count per service) is preserved as a custom numeric field. If no quoting workflow is used, the bundle definition is documented for the customer's admin to configure in GoHighLevel's custom fields.

Bizstim payment records (amount, date, client association, currency) map to GoHighLevel Invoices if the customer uses GoHighLevel's native billing, or to custom Opportunity fields (payment_amount, payment_date, payment_status) if the business tracks payments as deal custom fields. We extract the full payment history and flag any partial payments or credits for the customer's admin to review during reconciliation.

Bizstim User records (login and role data) map to GoHighLevel Users by email match. Owner and assignee mappings from client and practitioner records resolve against the User table. Any Bizstim User without a matching GoHighLevel User is placed in a reconciliation queue for the customer's admin to provision before record import resumes.

Bizstim Staff records mirror Practitioner data and are deduplicated against the Practitioners extraction using staff_id. We consolidate Staff and Practitioners as a single migration object to avoid duplicate Contact records in GoHighLevel. The deduplication key is staff_id.

Bizstim client availability windows (minTime, maxTime, slotDuration, sessionLimit) are extracted as structured availability rules from the client record. We map these to GoHighLevel Appointment Types configured per practitioner (Location field set to the practitioner Contact) with duration matching slotDuration. SessionLimit is noted as a custom field on the Appointment Type for the customer's admin to set the maximum bookings per window in GoHighLevel's calendar settings.