Migrate from MeasureSquare to HubSpot

MeasureSquare leads and customers map directly to HubSpot contacts. We preserve the original create date as a custom datetime field because HubSpot's Createdate reflects the migration import date, not the source record date. Owner assignment resolves by email match against HubSpot users.

MeasureSquare company records map 1:1 to HubSpot company records. Company hierarchies (parent/child) in MeasureSquare map to HubSpot's parent company field. Multi-location companies collapse to one HubSpot company per location unless your team specifies otherwise.

MeasureSquare deals (quotes) map to HubSpot deals. Deal name becomes the deal name in HubSpot. Pipeline stage values in MeasureSquare — such as Bid Sent, Proposal Under Review, or Awarded — map to HubSpot deal stage values; custom pick-list values are defined in HubSpot before migration runs.

MeasureSquare quote headers migrate as HubSpot deals with the total amount preserved. Quote line items (flooring products, labor rates, materials) migrate as HubSpot line items attached to the deal. Each line item inherits the product reference from the MeasureSquare product database.

MeasureSquare purchase orders have no native HubSpot equivalent. We create a Purchase Order custom object with fields for vendor, PO number, status, total amount, and linked deal. The object must be created in HubSpot before migration; we provide the schema specification.

MeasureSquare work orders carry installer assignment, jobsite address, job date, scope of work, and status. We create a Work Order custom object in HubSpot and map these fields directly. JobTrakr production tracking data (jobsite production logs) requires additional custom fields on the object.

MeasureSquare's schedule-of-values, change order tracking, and actual-vs.-estimated cost data has no HubSpot equivalent. We create a Job Costing custom object linked to the HubSpot deal, with fields for phase, estimated cost, actual cost, variance, and change order amount. This requires HubSpot Enterprise or a custom objects plan.

MeasureSquare product databases store flooring SKU, material type, vendor, slab layout configuration, and unit pricing. These map to HubSpot products with custom fields for flooring-specific attributes. The product catalog must be created in HubSpot before the deal migration runs so line items can reference product IDs.

MeasureSquare tasks (follow-ups, internal reminders, vendor outreach) map directly to HubSpot tasks. Original timestamps and owner assignments are preserved. Tasks linked to specific deals carry the deal association in HubSpot.

MeasureSquare files attached to quotes, work orders, and purchase orders — including floor plan diagrams and bid proposal PDFs — are downloaded and re-uploaded to HubSpot Files. Files are linked to the corresponding deal or custom object record. File size limits per HubSpot apply (25MB default per file).

MeasureSquare vendors map to HubSpot companies flagged with a Vendor_Type__c custom property. This lets your team filter the HubSpot company list by vendor vs. customer vs. prospect role. Vendor pricing request records from MeasureSquare link to the vendor company in the custom Purchase Order object.

MeasureSquare bid proposal templates with floor plan diagrams, product layouts, and custom branding do not migrate. We export template definitions as a PDF reference for your HubSpot admin to rebuild using HubSpot's proposal tool or a third-party document generation app. This is a manual rebuild step we document in the migration plan.