Migrate from MeasureSquare to Twenty CRM

MeasureSquare person records map directly to Twenty People. The name, email, phone, and job-title fields migrate as direct equivalents. The primary company link resolves via companyId — the company record must exist in Twenty before People are imported so foreign-key references resolve correctly.

MeasureSquare company records migrate to Twenty Companies with domain/website, industry, and address fields as direct equivalents. Parent-company hierarchies (if used) map to the twenty Companies ParentId relationship. Multi-contact companies collapse to one primary People link with additional contacts attached via the twenty relationship model.

MeasureSquare deals migrate to Twenty Opportunities. The deal name, amount, close date, and ownerId all map directly. Pipeline stages map to Twenty Opportunity stage values via value-by-value mapping. Each MeasureSquare pipeline becomes a distinct set of stages in Twenty — stage probabilities are preserved as custom numeric fields for reporting continuity.

MeasureSquare pipeline stage names (e.g., Prospecting, Bid Sent, Under Review, Awarded, Lost) map to Twenty Opportunity stage values. We map each stage name by value and reapply any probability percentages as custom fields since Twenty's default stage probabilities may differ from MeasureSquare's custom stage weights.

MeasureSquare bid proposal status (Sent, Viewed, Signed, Expired) has no native equivalent in Twenty. We migrate the most recent bid proposal status as a custom pick-list field (Bid_Proposal_Status__c) on Twenty Opportunities, preserving the current state of each deal's proposal lifecycle. Historical bid events — timestamps of when a proposal was sent, viewed, or signed — migrate as Opportunity activity notes attached to the relevant record. This approach maintains a chronological proposal history without requiring a separate custom object.

MeasureSquare's Contractor Pro and Complete tiers include vendor pricing request tracking for material cost lookup during the estimating process. These become custom fields (Vendor_Pricing_Request_Status__c, Vendor_Pricing_Request_Date__c) on the relevant Twenty Companies or Opportunities record. Request details — requested materials, quantities, and vendor responses — migrate as note attachments on the same record so the context stays with the deal or account that initiated the request.

MeasureSquare installation scheduling data (assigned date, crew, jobsite address) migrates as a Twenty custom object (Installation_Schedule__c) linked to the Opportunity, or as Tasks with custom fields if the schedule is simple. Complex schedule hierarchies become custom object records; single-install records use Tasks for faster setup.

MeasureSquare Contractor Complete's change order tracking migrates as a custom object (Change_Order__c) linked to Opportunities — capturing change order number, amount delta, approval status, and description. Each change order generates a unique Change_Order__c record with a sequential identifier, stores the dollar amount difference from the original deal value, records the approval workflow status (Pending, Approved, Rejected), and includes a description field for change justification. Change order history is preserved as child records with timestamps so the full revision timeline is auditable in Twenty.

MeasureSquare job costing data (material cost, labor cost, margin percentage, profit amount) migrates as custom numeric fields on Twenty Opportunities (Job_Cost_Material__c, Job_Cost_Labor__c, Job_Margin_Pct__c, Job_Profit__c). These enable post-migration margin reporting without requiring a dedicated job-costing module. The four-field structure captures the primary cost components from MeasureSquare's job-costing engine, letting finance teams calculate effective margins directly from the Opportunity record in Twenty or via a custom report pulling the numeric fields.

MeasureSquare notes on any record (Person, Company, Deal) migrate to Twenty Notes, preserving the linked record type, the original creation timestamp, and the author/owner. Notes on company records attach to the migrated Companies record in Twenty; notes on deals attach to the migrated Opportunity.

MeasureSquare tasks (follow-ups, reminders, to-dos) map to Twenty Tasks with title, due date, assignee, completion status, and linked record preserved. Original create timestamps migrate as custom datetime fields because Twenty's CreatedDate reflects the import time, not the original task creation date.

MeasureSquare owner IDs resolve to Twenty WorkspaceMembers by email match. Owners without a matching Twenty workspace email are flagged before migration begins — your team either creates the user in Twenty first or assigns a designated fallback owner. No record lands in Twenty without an assigned owner.

MeasureSquare's product and service catalog is an estimating-specific data structure with vendor SKUs, pricing matrices, and labor cost rates. Twenty has no native product or inventory object on its standard CRM tier. The catalog data does not migrate — it must be rebuilt in MeasureSquare (if kept) or entered into whichever estimating tool your team adopts post-migration.