Migrate from Briostack to Freshsales

Briostack FSM data has no native Freshsales equivalent — schema design decision required before migration

Briostack route plans, technician dispatch assignments, and work order line items don't map to any standard Freshsales object. You must decide before migration begins whether to create a Work_Order__c custom object linked to Deals, or to flatten work order data into custom fields on the parent deal. This decision affects how Freshsales reports on service history, how deals display in list views, and how your admin structures Freshsales page layouts. If you defer this decision, FlitStack will surface it during the sample migration and hold the full run until your team confirms the schema approach. Choosing a custom object gives better historical depth; choosing flat fields simplifies deal views but loses per-visit granularity.

Briostack custom field data types may not map directly to Freshsales field types

Briostack custom fields on any object can include date arithmetic fields, formula fields, and multi-select pick-lists that have different behavior in Freshsales. Multi-select pick-lists in Briostack map to Freshsales multi-select pick-lists, but formula fields and computed fields in Briostack are calculated at read time — those values export as static text and carry over as text fields in Freshsales. Your admin should review all Briostack custom field types before the mapping phase and flag any that reference other Briostack objects, since Freshsales custom objects have different relationship cardinality rules. Fields that reference deleted Briostack records become null and require cleanup before import.

Briostack workflows, automations, and routing rules do not migrate and must be rebuilt

Briostack scheduling automations — appointment reminder triggers, technician dispatch rules, SMS notifications tied to job status changes, and recurring service cadence automations — are built on Briostack's FSM event model and have no Freshsales equivalent. Freshsales workflows operate on Lead, Contact, Account, and Deal events using the Freshsales workflow builder. We export your Briostack workflow definitions (trigger conditions, actions, and recipient rules) as a reference document. Your Freshsales admin uses this to rebuild equivalent automations in Freshsales's workflow builder. Note that Freshsales does not have scheduling-triggered automations — appointment reminders require an integration with a calendar tool or a Freshworks add-on.

Briostack's per-user and per-technician pricing model does not map to Freshsales per-seat model

Briostack pricing differentiates between office users and field technician seats, with FSM features tied to technician accounts. Freshsales uses a flat per-seat model where all users get the same feature set per plan tier. If your Briostack account has more technician accounts than office CRM users, your Freshsales seat count may be lower — but you lose the technician-field-app capability that Briostack includes. Freshsales does not offer a technician mobile app for field service; your technicians would need either the Freshsales mobile app (designed for sales reps, not field techs) or a separate FSM tool. Budget for this gap if your field team needs mobile job management after migration.

Briostack invoice and payment records require a custom object — Freshsales Deals do not replace accounting data

Briostack stores invoices, payment records, and accounting transactions linked to jobs. Freshsales Deals handle quote-to-cash for sales opportunities but do not store historical invoice records or payment method data. We migrate Briostack invoices as a custom Invoice__c object linked to the Account and associated Deal, preserving invoice number, date, amount, payment status, and payment method. However, Freshsales does not have accounts payable or financial reconciliation built in — invoice records are for reference and do not trigger Freshsales billing workflows. If your accounting team relies on Briostack invoices for bookkeeping, plan for a separate accounting integration (QuickBooks, Xero) post-migration.