Migrate from Shark Byte CRM to Twenty CRM

Shark Byte Customer records (representing end-client organizations or homeowners) map to Twenty Company. Standard fields including company name, address, and service history transfer as Company displayName, address fields, and custom fields. We use company name as the dedupe key during import and extract any service history as a custom field group on the Company record. Customer custom fields migrate to Company custom fields created via the /metadata API before import.

Shark Byte Contact records (individual points of contact at each Customer site) map to Twenty Person. Fields including name, phone, email, and role transfer directly. Note that Twenty's Person object has been flagged by the community (GitHub issue #13953) as missing standard fields like multiple phone types, job title, department, and social profiles out of the box. We create these custom fields via /metadata during schema setup if they exist in Shark Byte.

Estimates are the core product object in Shark Byte CRM, built using the platform's estimating engine with line items, labor rates, and material costs. Because Twenty has no native estimating object, we create a custom Estimate object via the /metadata API with fields for line items, contract-term bucket (1-3 year, 3-5 year, 10+ year), pricing logic, and linked Company. We preserve the original Shark Byte estimate metadata as custom fields and link each Estimate to its originating Customer (now Company) and Contact (now Person).

Shark Byte Proposals are generated from Estimates and include pricing, scope, and terms. We create a custom Proposal object in Twenty linked to the custom Estimate object via a lookup relationship. Proposal status, scope description, terms, and associated Contact transfer as fields. Signed proposal PDFs migrate as attachments linked to the Proposal record via ContentDocumentLink.

Service Agreements in Shark Byte represent recurring contracts tied to maintenance programs, analyzed across 1-3 year, 3-5 year, and 10+ year term buckets calibrated to the customer's historical data. We create a custom Service Agreement object in Twenty with fields for contract-term classification, start and end dates, pricing structure, and linked Customer and Contact. This is the most schema-dependent mapping because Shark Byte's term buckets are customer-specific.

Work Orders track individual jobs dispatched to technicians. Mobile building surveying tools in Shark Byte feed into Work Order creation. We create a custom Work Order object in Twenty with fields for status, assigned technician, line items, and linked Customer and Contact. Survey photos and site condition attachments migrate as ContentDocument records linked via ContentDocumentLink to the Work Order.

Shark Byte CRM supports file attachments on Customer, Estimate, Proposal, and Work Order records. We extract all available attachments at original resolution where possible and migrate them as ContentDocument records in Twenty, linked to the appropriate parent record via ContentDocumentLink. Mobile survey images may have inconsistent compression levels and missing EXIF metadata depending on the device used; we note this during extraction and preserve filenames and upload timestamps as metadata on the ContentDocument record.

Shark Byte CRM supports custom fields on primary objects, particularly on Estimates and Service Agreements to accommodate industry-specific data like equipment specifications or contract classification. We create matching custom fields on Twenty's Company, Person, and custom objects via the /metadata API before data import. Each custom field is created with the correct field type (string, number, date, picklist) matched from the Shark Byte field definition.

Shark Byte Owner records (technicians and sales users assigned to Estimates, Work Orders, and Proposals) map to Twenty User records. We resolve owners by email match where possible. Any Shark Byte Owner without a matching Twenty User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignments on Work Orders and Estimates transfer as custom owner fields or assigned-to relationships depending on the custom object schema.

Shark Byte's pipeline stages and status conventions for Estimates, Proposals, and Work Orders are custom to the account and do not map to any standard Twenty field. We create custom picklist fields on each custom object representing the relevant stage values (e.g., Estimate status: Draft, Submitted, Accepted, Lost; Work Order status: Scheduled, In Progress, Completed, On Hold). The customer approves the stage mapping during scoping.