Migrate from Briostack to Nutshell

Service-frequency and recurring-billing fields have no native Nutshell home

Briostack's recurring service model (monthly treatments, quarterly contracts) stores cadence and subscription status as native deal or customer properties. Nutshell Deals track one-time sales pipeline stages and do not support a native recurring-billing interval field. FlitStack preserves recurring frequency as a custom text field on the Nutshell Deal record (Recurring_Frequency__c), but Nutshell's native reporting cannot segment deals by subscription cadence without custom reporting views. Teams relying on Briostack's recurring revenue dashboard will need to build an equivalent report in Nutshell's reporting module or export the custom field data to a spreadsheet.

Appointment and route data requires transformation into Nutshell Activities

Briostack appointment records carry technician assignment, service type, chemical application details, and route-zone tags. Nutshell has no appointment or service-visit object — completed visits become completed Tasks with a description block, and scheduled visits become Events. Route optimization data (zone, sequence, drive time) cannot be represented natively in Nutshell's Activity model. FlitStack maps appointment data to Nutshell Activities and preserves route-zone information as a custom text field on the linked Person record, but Nutshell's calendar views cannot replicate Briostack's route-optimization display without a third-party integration.

Briostack API rate limits can extend extraction time on larger databases

Briostack's Free tier caps API usage at 350 requests per month, which is insufficient for a full data extraction on any non-trivial database. Basic tier provides 750 requests per day — enough for small databases but potentially requiring multiple days of extraction for record sets above 10,000. FlitStack implements request pacing and checkpoint resumption so that extractions interrupted by rate-limit responses resume from the last checkpoint rather than restarting. Teams on the Free tier should upgrade to Basic or Premium before migration day to avoid extending the extraction window.

Chemical usage and compliance logs become opaque custom fields in Nutshell

Pest control businesses that use Briostack's chemical usage tracking for regulatory compliance will find that Nutshell has no structured compliance-log object. FlitStack migrates chemical product name, application rate, and treatment area as a long-text custom field on the Person record (Chemical_Usage_Log__c), JSON-encoded for maximum information density. However, this field cannot be queried in standard Nutshell reports and is not indexed for filtering. Businesses with strict pesticide-application record-keeping requirements should export Briostack's compliance logs separately and store them in a dedicated compliance document system alongside the Nutshell migration.

Customer-to-company linking in Nutshell requires pre-planning for N:N relationships

Briostack allows a single customer to be associated with multiple company accounts (e.g., a property management firm managing multiple commercial properties). Nutshell People can be linked to one primary Company with additional associations managed via the Person-Company relationship feature. FlitStack migrates the most-recently-modified Briostack company as the primary Nutshell Company link and surfaces remaining company associations as notes or custom fields. If your business relies heavily on N:N customer-to-company relationships, the Nutshell admin should review the association model before migration and document which companies are business-critical for reporting.