Migrate from Service Buddy to Twenty CRM

Service Buddy clients map directly to Twenty People records. Client first name, last name, email, phone, address, and job title transfer as structured fields. Owner (staff member) resolves by email match against Twenty Workspace Members. Any additional custom properties on the client record, such as referral source or preferred contact method, migrate as custom fields on the People object to preserve the complete client profile.

Service Buddy company records — business name, domain, industry, employee count, address — map to Twenty Companies. Companies must be imported first in Twenty's sequence (Companies → People → Opportunities) so foreign keys resolve correctly during the migration. This sequencing ensures that when People records are loaded, they can reference their parent Company via the companyId foreign key, preventing import failures and orphaned records.

Service Buddy quotes map to Twenty Opportunities. Quote name becomes Opportunity name; quote amount maps to Opportunity.amount; quote status (Draft, Sent, Approved, Declined) maps to a custom Opportunity.stage field or Twenty's built-in stage pick-list. Original quote create date preserved as a custom datetime field.

Service Buddy jobs have no direct Twenty equivalent. We create a custom Job object in Twenty and map job name, description, status, assigned crew, scheduled date, and service type as structured fields. Job-to-task conversion (Twenty's standard Tasks) is an option for simpler setups.

BuddyPay invoice records (transaction ID, amount, payment method, status, date, card type, ACH trace) have no native Twenty equivalent. We create a Payment custom object linked to the People or Companies record. Payment status (Paid, Pending, Overdue) migrates as a select field; original invoice number preserved as a text field.

Service Buddy inventory with SKU, stock quantity, QR-code label data, vendor, and reorder level requires a custom object in Twenty. We map product name, SKU, stock level, vendor, purchase price, and measurement unit as structured fields. QR-code data (storage location, condition notes) migrates as text fields on the same record.

Service Buddy service area routing (for installation scheduling) has no direct Twenty equivalent. We preserve service area zip codes, region names, and crew assignments as custom fields on the relevant Company or Job Task record for reference — this requires a manual review to determine the best placement for your workflow.

Service Buddy tracks rug cleaning stages (Intake, Cleaning, Repair, Storage, Pickup) per job. We map these as a custom multi-select or select field on the Job Task or custom Job object in Twenty, preserving the current stage value and stage-entered timestamps as separate datetime fields.

Service Buddy's two-way QuickBooks Online sync (invoice, payment, chart of accounts) has no Twenty equivalent. We export the QBO sync records separately and recommend a post-migration reconciliation step with your accountant to ensure financial continuity. No QB data migrates into Twenty automatically.

Service Buddy stores photos, documents, and condition notes attached to jobs and clients. Twenty's CSV import does not carry file attachments. We extract attachment URLs and filenames, then re-upload them via Twenty's GraphQL API post-import or provide a file manifest for manual re-upload. Inline images in notes are downloaded and re-hosted.

Service Buddy installer and crew profiles (name, phone, role) map to Twenty Workspace Members. We resolve each by email match against Twenty users. Crew assignments on jobs migrate as the task Assignee field. Unmatched crew members are flagged before migration for manual user creation.

Service Buddy text notes and communication logs on clients, companies, and jobs migrate as Twenty Notes linked to the corresponding People, Company, or Task record. Original create date and author preserved on each note. Rich-text formatting simplifies to plain text during migration to ensure compatibility with Twenty's note rendering engine while retaining the core message content.