Migrate from Briostack to Zoho CRM

Briostack Customer maps to Zoho CRM Account. The primary service address becomes the Account's street address; additional service locations for the same customer become child Accounts linked via the Parent Account field. We use the customer name as the Account Name and preserve the original Briostack customer ID as External_ID__c for traceability.

Briostack leads that have not converted to customers migrate as Zoho CRM Leads. Name, email, phone, company name, and source are mapped directly. Lead status is translated to Zoho's pick-list (Not Contacted, Attempting Contact, Converted) and the original lead creation date is preserved in a custom datetime field.

Briostack contact records (individuals associated with a Customer) migrate to Zoho CRM Contacts. Each contact is linked to the corresponding Account via Account_Name. Mobile phone, email, title, and address fields map directly; notes are migrated as Zoho Notes attached to the Contact record.

Briostack Job maps to Zoho CRM Deal (the Opportunities module). Job number is stored as a custom External_Job_ID__c field. Job status (Booked, In Progress, Completed, Cancelled) maps to Zoho Deal Stage values configured within your Blueprint sales process. The service location is linked via the Account_Name lookup to the corresponding service-location Account record.

Briostack line items on a Job (service type, quantity, chemical used, pricing) either map to Zoho Products if a product catalog exists or are stored as a JSON-formatted custom field (Line_Items_JSON__c) on the Deal. Unit price and quantity are preserved. If products are created, we link them via the Deals_Products relationship table.

Briostack technician assignments on jobs do not have a native Zoho CRM equivalent. We resolve each technician by email match against Zoho CRM users — matched technicians are stored as a lookup field (Assigned_Technician__c) on the Deal. Unmatched technicians are flagged and stored as a text custom field (Technician_Name__c) for manual assignment after migration.

Briostack custom fields on Customer objects (such as preferred service frequency, account tier, or billing preference) are created as Zoho CRM custom fields on the Account module. Multi-select pick-list values are preserved as multi-select fields in Zoho where supported, or stored as a semicolon-delimited text field for manual normalization post-migration.

Briostack job-specific custom fields — service type, chemical log, access notes, pest category — are created as custom fields on the Zoho Deal module (e.g., Service_Type__c, Chemical_Log__c, Pest_Category__c). Date fields are stored as Zoho date fields; long-text fields map to Zoho's multiline text type.

Briostack activity records — call logs, site visit notes, internal comments — migrate as Zoho CRM Tasks (for calls and generic activities) and Notes (for rich-text comments). Original timestamps, owner email, and parent record links are preserved. Completed visits with duration map to Zoho Events with start/end times.

Briostack file attachments on customers, contacts, or jobs are downloaded and re-uploaded to Zoho CRM as Attachments linked to the corresponding Account, Contact, or Deal record. Files exceeding Zoho's 25 MB per-attachment limit are flagged and documented for manual upload.

When a single Briostack Customer has multiple service addresses, we create one parent Account (the primary customer) and N child Accounts (one per service location) linked via the Parent Account field. The primary address from Briostack becomes the parent Account; each additional address becomes a child Account with its own Contact records and linked Deals.