Migrate from Bizstim Business Management Software to Microsoft Dynamics 365 Sales

Bizstim Client records map to Salesforce Contact for qualified clients or Salesforce Lead for unqualified prospects. We resolve the split based on whether the client has an associated Opportunity in Bizstim (indicating sales-qualified status) or only session booking records. Client address, phone, email, and availability slot fields (minTime, maxTime, slotDuration, sessionLimit) map to standard Contact fields or custom Contact fields for scheduling preference data. The original Bizstim client ID is preserved in a custom field bizstim_client_id__c for audit reconciliation.

Bizstim Practitioner records map to Microsoft Microsoft Dynamics 365 Sales User accounts. We resolve by matching practitioner email against the Azure Active Directory-backed user table in the destination tenant. Practitioner wage settings (practitioner_wage, payment rates) have no native Microsoft Dynamics 365 Sales equivalent and are preserved in a custom field practitioner_wage__c on the User record for the customer's admin to extend into a compensation model post-migration. Bizstim staff_id is preserved in a custom field for reconciliation.

Bizstim Service records map to Salesforce Product2 entries. The group_id field that organises services into bundles maps to a custom field service_group_id__c. Session count (group_num) and practitioner wage defaults stored in the Service record become custom Product fields service_session_count__c and default_practitioner_wage__c. Service cost maps to StandardPrice on the Product2 PricebookEntry. Service packages (bundles of sessions) are delivered as a written configuration guide for the customer's admin to build as a product bundle in Dynamics 365 CPQ if required.

Bizstim service_group_names table entries link services via group_id. Service packages are exported as a group-to-service lookup table and delivered as a structured CSV alongside the Product2 import. The customer's Dynamics 365 admin configures the bundle structure (if using Sales Hub Enterprise with CPQ) or documents service packages in a custom configuration object. We do not create CPQ bundle configurations as part of standard migration scope.

Bizstim Payment records (amount, date, client association, currency) map to Microsoft Dynamics 365 Sales Opportunities with Closed-Won status for paid transactions. Payment history is preserved as OpportunityLineItem entries on closed Opportunities, with the original payment date stored in a custom field original_payment_date__c. Outstanding or pending payments do not map to any standard Microsoft Dynamics 365 Sales object and are delivered as a structured CSV for the customer's admin to action in Dynamics 365 Finance or a separate billing tool.

Bizstim client availability rules (minTime, maxTime, slotDuration, sessionLimit) are extracted as structured data and delivered in a configuration guide. These do not map to a native Microsoft Dynamics 365 Sales object because sales CRMs do not typically store per-contact scheduling windows. The guide maps each availability rule to Outlook calendar booking rules, Microsoft Bookings app configurations, or Dynamics 365 Resource Scheduling custom fields depending on the customer's intended workflow post-migration.

Bizstim Users (login and role data) are cross-referenced against Practitioner records. Bizstim role data (admin, practitioner, staff) maps to a custom field bizstim_role__c on the Dynamics 365 User record. Role-based access configuration in Dynamics 365 (security roles, field-level security) is delivered as a written configuration plan for the customer's admin to implement post-migration.

Bizstim Staff records are deduplicated against Practitioner records by staff_id and merged into a single migration object. Non-practitioner staff members (billing staff, coordinators) without practitioner_wage associations map to Dynamics 365 User records with a custom field staff_type__c to distinguish them from sales practitioners.