Migrate from Briostack to HubSpot

Briostack client records map directly to HubSpot contacts. The client's name, phone, email, and address fields translate to HubSpot contact properties. Primary service location becomes the contact's default address. Clients without email addresses are flagged for manual review before migration.

Briostack clients who represent commercial accounts (multiple locations, purchase orders, contract service) map to HubSpot companies with the company name as the account name. The commercial billing address becomes the company address. Residential clients collapse to contacts without a company association.

Briostack work orders map to HubSpot tickets for service history visibility. Ticket subject pulls from the service type (e.g., 'Quarterly pest control — Commercial Kitchen'). Ticket status maps from Briostack work order status (Scheduled, In Progress, Completed, Cancelled). Original work order ID preserved as Source_System_ID__c.

Completed Briostack job records — including service type, chemicals applied, technician notes, and resolution — merge into HubSpot engagement notes on the associated contact. Job completion timestamps are preserved. Each job record generates one note entry on the primary contact; multi-technician jobs generate multiple note entries.

Briostack service types (e.g., Termite Treatment, Bed Bug Heat Treatment, Lawn Fertilization) have no native HubSpot equivalent. We create a Service_Type__c pick-list on the Ticket object. Values are mapped from Briostack's service-type taxonomy. If Briostack uses custom service types, those become additional pick-list values.

Briostack technician records map to HubSpot users by email match. Technician name and phone become user profile fields. Briostack technician specializations (e.g., 'licensed for Termite WDO') migrate as a custom text field on the HubSpot user for routing reference. Unmatched technicians are flagged for team assignment before migration.

Briostack invoices linked to closed work orders map to HubSpot deal line items. Line item name pulls from the service type; quantity reflects the number of treatments; price reflects the invoice amount. Payment status is not a native HubSpot field — it is stored as a custom pick-list (Invoice_Payment_Status__c) on the associated deal.

Briostack recurring service plans (e.g., 'Quarterly commercial pest control — 4 visits/year') have no direct HubSpot equivalent. We preserve the plan name, frequency, and next service date as custom fields on the company or contact record. HubSpot workflows can be configured to trigger reminders based on those fields post-migration.

Briostack route and scheduling data (appointment window, route sequence, technician assignment) has no native HubSpot object. Appointment window and route sequence migrate as custom text fields on the ticket (Appointment_Window__c, Route_Sequence__c). HubSpot's calendar integration can be configured manually for appointment tracking.

Briostack stores custom properties per client (e.g., 'Preferred Contact Method', 'Gate Code', 'Pet Information'). Each custom property requires a corresponding custom field on the HubSpot contact. Field type (text, number, date, pick-list) is preserved. If Briostack uses a pick-list, HubSpot picks are created with the same values.

Briostack custom properties on job records (e.g., 'Chemical Used', 'Sq Footage Treated', 'Warranty Period') migrate to HubSpot ticket custom fields. Chemical usage data migrates as text fields to preserve brand names; numeric fields (sq footage, warranty months) map as number fields. If the same custom property appears across all jobs, it becomes a standard ticket field.