Migrate from Contractor+ to HubSpot

Contractor+ clients store contact details and company affiliation in one record. FlitStack splits the record: contact fields map to a HubSpot Contact, and company name/domain map to a HubSpot Company. The Contractor+ client-to-company link is preserved as the Contact's primary Company association in HubSpot.

Contractor+ leads map directly to HubSpot Contacts. FlitStack applies a default lifecycle_stage value of 'lead' during migration; your team can update lifecycle stage values after import based on qualification status. Source lead status is preserved as a custom property for reporting continuity.

Contractor+ jobs are the core project object. Each job maps to a HubSpot Deal where the deal name uses the job title, the deal amount pulls from the latest estimate value, and the deal stage maps from the Contractor+ job status field. Owner assignment resolves by email match against HubSpot users.

Contractor+ job status values (e.g., Scheduled, In Progress, On Hold, Completed, Invoiced) map one-to-one to HubSpot deal stages. FlitStack creates the destination deal stages before migration and maps each status value explicitly. Any unmapped status values are flagged for manual review before the migration runs.

Contractor+ estimates contain line items with materials, labor, and markup. FlitStack maps the estimate total to the HubSpot Deal amount and creates individual line items on the deal using HubSpot's Line Item object, linking each to the target Deal by deal ID. Estimate-specific fields like validity date and accepted status migrate as custom properties on the deal.

Contractor+ invoices map to HubSpot Deals where the invoice status (Paid, Partial, Overdue) becomes a custom pick-list property on the deal. Paid invoices retain their payment date and amount; partial payments are tracked via the deal's associated line items and a custom paid_to_date__c field.

Contractor+ client portals let homeowners view estimates, invoices, and job status directly. HubSpot has no native customer-facing portal equivalent. We preserve the portal access configuration as a custom property (had_client_portal__c) so your team can identify which clients had portal access and build a replacement using HubSpot's member portal or a third-party tool.

All Contractor+ custom fields on clients and jobs become HubSpot custom properties. FlitStack creates the properties in HubSpot before migration using snake_case naming convention (e.g., insurance_claim_number for a Contractor+ field of the same name). Custom field data type is preserved: text, number, date, and pick-list fields map to their HubSpot equivalents.

Contractor+ owner and team member records resolve to HubSpot users by email match. FlitStack validates that each Contractor+ owner has a corresponding HubSpot user before migration; unmatched owners are flagged with a fallback assignment to a designated HubSpot admin user.

Contractor+ file attachments on jobs and clients are downloaded and re-uploaded to HubSpot Files, associated to the corresponding contact or deal record. File size limits apply (HubSpot default 25MB per file); oversized files are flagged for manual review. After upload, files remain accessible via the HubSpot Files dashboard.

Contractor+ stores sub-contractor references on jobs. HubSpot has no native sub-contractor field on deals. FlitStack creates a custom property (sub_contractor__c) on the Deal object and maps the sub-contractor name from Contractor+ as a text value. If sub-contractors are tracked as separate Contractor+ clients, FlitStack creates them as HubSpot contacts and links them via a custom junction association.

Contractor+ live local material cost data is Contractor+-specific and not natively available in HubSpot. FlitStack maps the most-recently-used material prices from Contractor+ as a custom text property on deal line items for reference. Rebuilding live material cost lookups requires a third-party integration or custom development in HubSpot.