Migrate from Briostack to Salesforce Sales Cloud

Briostack customers map directly to Salesforce Accounts. The customer's primary service address becomes Account.BillingAddress. If the Briostack customer record includes a company name, it lands as Account.Name; sole-proprietor records with personal names become Account.Name with a note for the admin to create a Contact separately.

Briostack customer records that include a named individual (homeowner or business contact) map to Salesforce Contacts. Each Contact requires an AccountId — we link to the migrated Account record. Primary phone and email map directly; other contact details become custom fields if no standard Salesforce field exists.

Commercial customers in Briostack with a registered business name map 1:1 to Salesforce Accounts. Multi-location commercial accounts (branch offices) are mapped to child Accounts via ParentId — the top-level company record migrates first, then branches are linked. Each child Account preserves the original Briostack branch identifier in Source_System_ID__c for reconciliation and future delta-pickup runs.

Briostack leads (prospects without a service agreement) migrate as Salesforce Leads. Lead source, status, and rating map to Salesforce standard fields. Unconverted Briostack leads keep their original create date preserved in Original_Create_Date__c since Salesforce sets CreatedDate at migration time. The original Briostack lead ID is stored in Source_System_ID__c for traceability and de-duplication during subsequent migration runs.

Briostack work orders map to Salesforce Cases representing individual service visits. Case.Status reflects the work order completion state. Each work order generates one Case; recurring service agreements may generate multiple Cases keyed by scheduled date. Case.Origin maps to 'Field Service' and Case.Type maps to the treatment type from Briostack.

Individual treatment line items within a Briostack work order map to a custom Field_Service_Treatment__c object. This captures chemical product name, EPA registration number, application rate, and technician notes. The object has a lookup to the parent Case so each treatment is traceable to its service visit.

Briostack route objects capturing daily technician schedules and stop sequences migrate as a custom Route__c object. Each Route__c has a Date__c field, a Technician__c lookup to the Salesforce user, and a relationship to the Cases assigned for that day. Route optimization logic (Briostack's built-in algorithm) does not transfer and must be rebuilt in Salesforce Flow or an AppExchange routing app.

Briostack invoices map to Salesforce Orders or a custom Invoice__c object depending on the destination org's quote-to-cash configuration. Invoice line items map to OrderProducts. Briostack's QuickBooks sync data is preserved as a custom QuickBooks_ID__c field on the Order record for reference reconciliation.

Briostack estimates and quotes map to Salesforce Quotes attached to Opportunities or directly to custom Quote__c objects. The estimate amount, status, and validity period map to Salesforce standard fields. If the destination org uses Salesforce CPQ, estimates map to CPQ Quote objects with product line items.

Briostack payment records capturing amounts paid, payment method, and date map to a custom Payment__c object. Each Payment__c is linked to the corresponding Order or Invoice record via a lookup relationship. This preserves the 11% average collections improvement metric as historical payment data in Salesforce.

Briostack service agreements with recurring billing terms map to Salesforce Contracts attached to the Account. Contract start and end dates, annual revenue, and billing frequency map directly. Auto-renewal flags map to Contract.Status = 'Activated' with a follow-up task generated at renewal.

Briostack logged calls, emails, and field visit notes map to Salesforce Tasks with Type = 'Call', 'Email', or 'Note'. Visit notes with timestamps map to Events with the visit date as the Event start time. Original timestamps and owner (technician) preserved via WhoId and OwnerId.

Briostack chemical tracking fields (product name, EPA registration number, application rate, re-entry interval) have no Salesforce standard equivalent and are created as custom fields on the Field_Service_Treatment__c custom object. Field type is Text for product names and Numbers for application rates.

Briostack pest type and treatment category pick-lists are recreated as custom pick-list fields (Pest_Type__c, Treatment_Category__c) on the Case or Field_Service_Treatment__c object. Value-by-value mapping is applied for each distinct pick-list value found in the Briostack export. All mapped values are validated against the destination org's pick-list definitions, and unmapped values are flagged for custom value addition before migration.

Briostack technician and owner records are resolved by email match against Salesforce Users. Unmatched technicians are flagged before migration — the admin either creates Salesforce users first or assigns records to a fallback owner. Owner IDs from Briostack are preserved in Source_System_Owner_ID__c for audit trails.