Migrate your Briostack data

Briostack's Customer object holds contact data, address, service history, and payment information. We migrate Customers with full field fidelity using the Public API. Global Customer Search and Customer Summary Page data translate directly to standard Contact/Account models at the destination.

Lead records include source, status, and assigned territory data. Briostack's Lead Management module exposes these via API. We preserve lead stage and assignment during migration and flag territory assignments for remapping if the destination does not support geographic territories.

Appointment records include service cadence, scheduled date/time, assigned technician, and customer association. We map these to Jobs or Service Records at the destination. Appointment sequencing logic (custom cadence rules) is stored as property data and translates with field-level mapping.

Route assignments and optimization data are Briostack-native concepts. We extract route groupings and technician-to-appointment assignments but note that routing algorithms do not port — only the assignment outcome (which technician visits which customer on which day) is preserved. Route optimization rules must be reconfigured at the destination.

Technician profiles include name, contact info, certifications, and territory assignments. We migrate Technicians as Users or Technicians at the destination. Active/inactive status is preserved; schedules are derived from Appointment assignments rather than stored as standalone objects.

Invoice records include line items, totals, payment status, and customer association. We migrate open and historical invoices via the API. QuickBooks integration exports invoice data cleanly. Closed invoices are migrated as read-only records; open invoices are flagged for reconciliation post-migration.

Payment records link to invoices and customers. We migrate payment history including method, amount, date, and reference number. Post-migration reconciliation is required for partial payments and payment plan records.

Compliance-related chemical application records require field-level mapping because destination CRMs often lack a dedicated chemical tracking object. We map these to custom fields, treatment records, or notes depending on the destination schema. Regulatory compliance data should be reviewed by the customer before import.

Briostack's Marketing Automation module stores campaign configuration, audience rules, and campaign metadata. Campaign templates and audience segments do not transfer natively. We migrate campaign names, status, and targeting criteria as custom properties; the automation logic must be rebuilt at the destination.

Briostack dashboard configurations, saved report layouts, and custom reporting filters are platform-specific and stored in proprietary formats. We do not migrate dashboard configurations. We export underlying data so dashboards can be rebuilt at the destination.

Briostack allows custom fields on customers, leads, and appointments. We migrate custom property names and values as standard fields or custom fields at the destination, depending on schema compatibility. Complex picklist or multi-select values require explicit mapping review.

Sales leaderboard configurations are Briostack-native display settings with no data equivalent. These are not migrated. Underlying sales activity data (deals, activities) is migrated normally so leaderboards can be rebuilt in the destination system.

QuickBooks sync records including invoice exports, payment imports, and account mappings transfer cleanly during migration. We map QB-linked accounts and chart-of-accounts references to the destination accounting connection if applicable.

Recurring service agreements and warranty records are stored as linked objects on the customer record. We migrate contract terms, pricing, and frequency. Contract templates and automated renewal settings must be reviewed and reconfigured post-migration.