Migrate from improveit 360 to HubSpot

Improveit 360 contacts migrate as HubSpot contacts. The contact's email address serves as the primary unique identifier for deduplication; phone number and address fields map directly to their corresponding HubSpot properties. During migration, duplicate contacts are flagged for manual review based on Improveit 360's duplicate-prevention records before final insertion into HubSpot. This ensures data quality while preserving all legitimate duplicate records that may represent different individuals.

Improveit 360 leads with no associated account route to HubSpot contacts with lifecycle_stage set to the Improveit 360 lead_status value. If lead_status = 'Closed Lost', the contact lands with lifecycle_stage = 'other' and a note flagging the lost status for sales-ops review.

Improveit 360 companies map directly to HubSpot companies. The company name, domain, industry, phone number, and address fields transfer directly to their HubSpot equivalents. Improveit 360's company-type classification—such as General Contractor, Supplier, or Subcontractor—maps to a HubSpot custom property created for segmentation and reporting purposes. This preserves the relationship context between contacts and their associated organizations.

Improveit 360 supports multiple-company associations per contact, reflecting real-world relationships where contacts may work with several organizations. HubSpot's many-to-many association model accommodates this natively—each Improveit 360 company-contact link creates a corresponding HubSpot association with role designation and is-primary flags preserved throughout the migration. This maintains the complex relationship graph that exists in construction and contracting environments.

Improveit 360 project opportunities become HubSpot deals. The project name maps to dealname, the estimated value maps to amount, and the target close date maps to closedate. Sale status navigation maps to a HubSpot custom property because HubSpot deal stages handle open/closed/win/loss natively.

Improveit 360 pipelines—such as Remodeling Pipeline, Service Pipeline, and Replacement Pipeline—map to separate HubSpot deal pipelines to maintain workflow separation. Each pipeline's unique stage set maps to the corresponding HubSpot pipeline's stages, preserving stage order, probability weights, and forecast categories as custom properties. This ensures that deal progression logic from Improveit 360 translates directly into HubSpot's pipeline management framework.

Improveit 360 stage names—such as 'Measure Scheduled', 'Proposal Sent', 'Contract Signed', and 'Won - Installation'—map to HubSpot dealstage picklist values on a per-pipeline basis. Probability percentages and forecast categories are re-applied based on HubSpot's stage configuration settings. Additionally, original stage-entered timestamps are preserved as custom datetime fields, allowing teams to analyze deal velocity and stage duration using the historical Improveit 360 timestamps.

Improveit 360 products (with unit price, cost, and category) migrate as HubSpot line items linked to deals. The product's cost and margin data map to custom properties on the line item since HubSpot line items lack a native cost field.

Calls, emails, meetings, and notes logged in Improveit 360 become HubSpot engagements with original timestamps, assigned owners, and body content fully preserved during migration. Each engagement is associated back to the relevant contact and optionally linked to the associated deal using HubSpot's engagement association API. This maintains the complete activity history that sales teams rely on for context during customer conversations and ensures continuity in relationship management.

Improveit 360 custom fields—such as trade_type, lead_source_channel, project_phase, and estimator_id—require HubSpot custom properties to be created in the HubSpot property settings before migration begins. Field data types including text, number, picklist, date, and checkbox map to their corresponding HubSpot property types. For picklist fields, values require value-by-value mapping when the available options differ between the two platforms to ensure accurate data translation.

Improveit 360 appointments map to HubSpot meeting engagements with original start times, end times, location details, assigned user, and attendee contacts fully preserved during migration. This includes in-person appointments, phone calls, and video conferences that were scheduled within Improveit 360. HubSpot's meetings-versus-calendar-sync behavior is documented for your administrator to configure the appropriate sync settings post-migration to avoid duplicate calendar entries.

Improveit 360 users are matched to HubSpot users by their email address, which serves as the unique identifier across both platforms. Unmatched owners are flagged in a pre-flight report before migration begins—your team can either provision HubSpot user accounts for these individuals first or assign their records to a designated fallback owner during the migration process. This ensures every record has an assigned owner in HubSpot from day one.

Improveit 360 file attachments—including photos, contracts, proposals, and permits—are downloaded and re-uploaded to HubSpot Files using the HubSpot CRM file upload API. Each file is then linked to the corresponding contact, company, or deal record using HubSpot's association API. File size limits are enforced during extraction, as HubSpot caps file uploads at 25MB per file—larger files require chunked upload handling.