Migrate from Estimate Rocket to Twenty CRM

FlitStack AI maps Estimate Rocket Clients to Twenty People records using email as the unique identifier. Client type and sales rep fields have no Twenty native equivalent — we create Client_Type__c and Sales_Rep__c custom fields. Phone, mobile, and address fields map directly to Twenty's People address composite fields.

Each Estimate Rocket project becomes one Twenty Opportunity. Project name maps to Opportunity name; estimated value and actual amount map to amount fields. Since Estimate Rocket tracks project phases (Proposal, Awarded, In Progress, Closed) but Twenty Opportunities use stage (New, Meeting Scheduled, Proposal Sent, Closed Won/Lost), we create a custom Project_Phase__c field to preserve the original Estimate Rocket phase value alongside Twenty's stage.

Estimate Rocket's item library holds materials and labor entries with unit price, unit cost, taxable flag, section, and type. Twenty has no native line-item child object on Opportunities. We create an Item custom object with fields for name, unit, description, unit_price__c, unit_cost__c, taxable__c, section__c, type__c, and a relation to the Opportunity. Items are migrated first, then linked to Opportunities by name match after both objects exist in Twenty.

Estimate Rocket internal notes and activity history (call logs, appointment notes) map to Twenty Notes and Tasks. Original timestamps and creator attribution are preserved. Estimate Rocket's Project Activity History log — which tracks every action inside the app — migrates as a series of Tasks with created_at and body fields so the full audit trail is queryable in Twenty.

Estimate Rocket stores file attachments on projects (images, PDFs, contracts). Twenty has no native file attachment mechanism on records. We re-upload files to Twenty's storage and store the file URL in a File_Link__c custom URL field on the associated Note or Opportunity. File names are preserved in a File_Name__c custom text field for reference.

Estimate Rocket users (full users and field users) become Twenty workspace members. Name and email map directly. User role and client assignment permissions have no Twenty equivalent — we store Role__c and Full_User__c (boolean) as custom fields on the Workspace Member record. Owners on Projects map to the OwnerId on the migrated Opportunity by email match.

Estimate Rocket stores client billing and job-site addresses separately. Both address sets migrate to Twenty's People address composite field. If a client has both billing and job-site addresses, the billing address becomes the primary address and job-site address is stored in a secondary custom address field or as a Note for reference.

Estimate Rocket's Schedule tab displays appointments and assignments on a calendar. Each appointment migrates as a Twenty Task with a due date matching the scheduled date, linked to the Project-as-Opportunity record. Appointment time-of-day is stored in a custom text field if Twenty's date-only due date loses that granularity.

Estimate Rocket supports project-level discount percentage and dollar amount. Twenty Opportunities have no native discount field. We create Discount_Pct__c (number) and Discount_Amount__c (currency) custom fields on the Opportunity to preserve the original discount applied to the project total. These fields ensure the final billed amount can be recalculated in Twenty if needed.

Estimate Rocket's estimate records (with line items, pricing, and status) are not exported as structured objects. We extract the estimate name, total amount, status, and date as fields on the linked Opportunity, and the full itemized estimate is stored as a Note attachment with a reference URL if Estimate Rocket's API exposes the document link. If the document link requires authentication, we store a reference note pointing to the source Estimate Rocket system for retrieval.