Migrate from Briostack to Twenty CRM

Briostack Customers map directly to Twenty People records through a straightforward field-level transfer. Core contact information including email addresses, phone numbers, physical addresses, and full names migrate as-is without transformation. The critical mapping involves the primary propertyId field, which converts to companyId in Twenty's relational model, establishing the link between the person and their associated company. For Customers that lack a Property association, they create standalone People records without company linkage.

Email addresses serve as the unique identifier for both Twenty imports and user matching throughout the migration process. FlitStack performs comprehensive email validation before data loading, checking format compliance and identifying any malformed or missing email addresses. Records with validation failures are flagged in a pre-migration exception report, requiring manual correction before the full migration run executes to prevent import errors.

Briostack Properties represent service locations and include detailed information such as physical addresses, property types, and access instructions for technicians. These map to Twenty Companies, with the site address stored in Twenty's companyAddress fields. When a single Customer has multiple Properties associated with them, each Property becomes a separate Company record while maintaining linkage to the same Person record, preserving the one-to-many relationship.

Briostack's address structure uses separate fields for street, city, state, and zip code, while Twenty's Company object employs address1, address2, city, state, zip, and country fields. Our extraction process parses the source address object and remaps each component into the corresponding Twenty field names, ensuring address data populates correctly in the destination schema without manual re-entry.

ServiceTickets have no direct Twenty equivalent. We create a ServiceTicket custom object in Twenty with fields for ticketId, pestType, treatmentCode, serviceDate, technicianId, and status. The custom object must be created in Settings → Data Model before the import batch runs.

Service ticket notes and technician comments consolidate into Twenty Notes linked to the associated Company record for unified service history. Each service entry creates a dedicated Note containing the service summary, pest type treated, treatment applied, and resolution details. The original service timestamps from Briostack are preserved during the merge, maintaining the complete audit trail for compliance and customer communication purposes.

Briostack Deals map directly to Twenty Opportunities, with deal name, monetary amount, current stage, expected close date, and assigned owner transferring without transformation. The critical relationship mapping converts Briostack's deal-to-property association into Twenty's Opportunity.companyId field, establishing the link between each opportunity and its associated service company record for complete relationship preservation.

Briostack deal stages including Prospect, Qualified, Proposal Sent, Won, and Lost map to corresponding Twenty Opportunity stage values through a direct value-mapping approach. Each Briostack stage name must have a matching stage option pre-created in Twenty's settings before migration execution to ensure accurate stage assignment and prevent import failures for undefined stage values.

Briostack owner and technician records resolve to Twenty workspace members through email address matching during migration preparation. When no matching email exists in Twenty, the owner receives a fallback assignment to a designated admin member and appears in a pre-migration exception report. This approach ensures Twenty's requirement that users must be invited and active before ownerId links can successfully resolve during import.

Briostack's marketing contact flag lacks a native equivalent in Twenty's standard object model, requiring preservation as a custom field solution. We create a boolean custom field (isMarketingContact__c) on the Person object to maintain this classification after migration. Any marketing segmentation logic originally configured in Briostack must be rebuilt using Twenty's workflow filters and automation tools post-migration for continued campaign targeting.

Briostack industry-specific fields — pest type, treatment code, chemical usage — require manual custom field creation in Twenty Settings → Data Model before the migration batch. We provide the field name, type, and pick-list options as a setup checklist. Fields not pre-created are skipped with a flag for post-migration review.

Files attached to Briostack ServiceTickets or Properties download during the extraction phase and re-upload as attachments to corresponding Twenty Notes linked to Company records. Twenty enforces a 10MB file size limit per attachment, requiring oversized files to be flagged for manual handling post-migration. A post-migration checklist documents each oversized file with its source record reference to ensure complete transfer without data loss.