---
title: "Housecall Pro to HubSpot Migration: Field Mapping & Rollback"
description: "Migrate Housecall Pro to HubSpot with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/crm/housecall-pro/to/hubspot"
---

# Housecall Pro to HubSpot migration

FlitStack AI migrates Housecall Pro to HubSpot by mapping every customer, job, estimate, invoice, and property-profile record into HubSpot's Contact, Company, and Deal objects — preserving original create dates, owner assignments, and line-item detail so your HubSpot reporting reflects the full service history from day one.

Short answer

FlitStack AI migrates contact + companies, deals, deal + line items, custom object: equipments and contact + hubspot users from Housecall Pro to HubSpot, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 48–72 hours for under 50,000 records.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See the field mapping →](https://flitstack.ai/migrations/crm/housecall-pro/to/hubspot#field-mapping)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

Source Housecall Pro ![](https://flitstack.ai/platforms-trim/housecall-pro.webp)

Destination HubSpot ![](https://flitstack.ai/platforms-trim/hubspot.webp)

Contact + Company Deal Deal + Line Items Custom Object: Equipment Contact + HubSpot User

Mapped field by field · sample run · one-click rollback

## What moves from Housecall Pro to HubSpot?

Housecall Pro is a field-service platform built around Customers, Jobs, Estimates, Invoices, and Property Profiles — objects designed for scheduling, dispatch, and field payments.

Read the full summary

HubSpot is a marketing and sales CRM built around Contacts, Companies, Deals, and Tickets. The migration maps Housecall Pro customers to HubSpot Contacts (with address, phone, email, and tag data), Housecall Pro jobs to HubSpot Deals (with stage mapped from HCP status, amount from total, and a custom job\_type property), Housecall Pro estimates to Deals with line items, Housecall Pro invoices to Deals with paid status, and Property Profile equipment data (item type, make, model, serial) to a HubSpot custom object. Housecall Pro's employee roster maps to HubSpot contacts with an 'Employee' role property — your admin assigns HubSpot logins manually after migration. FlitStack reads Housecall Pro via its public API (available on MAX plans) and writes to HubSpot via the HubSpot API. A test migration runs first with a field-level diff before the full cutover and delta-pickup window commits the final state.

direct

### Customer → Contact + Company

Housecall Pro customers map to HubSpot Contacts with name, email, phone, and address.

How it maps

The customer.company field maps to a HubSpot Company record; HubSpot links them via the Contact's primary company association. Multiple phone numbers (mobile, home, work) each map to their HubSpot equivalents.

direct

### Job → Deal

Housecall Pro jobs are the core operational record — they map directly to HubSpot Deals.

How it maps

The HCP job status (scheduled, in\_progress, completed, cancelled) maps to a HubSpot deal stage via a value-mapping table. Deal amount, close date, and description carry over directly. A custom job\_type property preserves the HCP Job Type name.

direct

### Estimate → Deal + Line Items

Housecall Pro estimates map to HubSpot Deals with line items representing each estimate line.

How it maps

The estimate total becomes the Deal amount; estimate status (draft, sent, approved, declined) maps to custom deal stage values. Line items carry description, quantity, unit price, and total per row.

direct

### Invoice → Deal

Housecall Pro invoices map to HubSpot Deals with the invoice total as the Deal amount.

How it maps

The payment status (paid, partially paid, overdue, void) maps to a custom payment\_status property. Tax and discount amounts carry as separate custom properties since HubSpot Deals have no native tax/discount fields. Note that HubSpot Deals are not formatted invoices — your team rebuilds invoice presentation in HubSpot or a connected tool.

custom\_field\_required

### Property Profile → Custom Object: Equipment

Housecall Pro Property Profiles (item type, make, model, serial number, install date, notes) have no native HubSpot equivalent.

How it maps

FlitStack creates an Equipment custom object in HubSpot with fields for each data point, linked to the Customer Contact record via a lookup relationship. Multi-item properties per address generate multiple Equipment records.

transformed

### Employee → Contact + HubSpot User

Housecall Pro employees (name, phone, email, role) map to HubSpot Contacts with an 'Employee' role property.

How it maps

If employees need HubSpot seat access, your admin creates HubSpot Users manually after migration — FlitStack preserves the email and name for matching. Housecall Pro certifications and documents are stored as file attachments on the Contact record.

******What moves 15 objects

Housecall Pro HubSpot

- Customer Contact 1:1
- Job Deal 1:1
- Estimate Deal 1:1
- Invoice Deal 1:1
- Property Profile Custom Object: Equipment transformed
- Employee Contact transformed

\+ 9 more in the mapping below

## How Housecall Pro and HubSpot differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

| Dimension                     | Housecall Pro                                                                                      | HubSpot                                                                                                           |
| ----------------------------- | -------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| Core object model             | Customers, Jobs, Estimates, Invoices, Property Profiles — designed for field dispatch and payments | Contacts, Companies, Deals, Tickets — designed for lifecycle marketing and sales pipeline management              |
| Custom fields                 | Housecall Pro does not support custom fields on any object (verified limitation)                   | HubSpot supports custom properties on every standard object; Enterprise allows custom objects                     |
| Job scheduling                | Jobs carry status (scheduled, in\_progress, completed, cancelled) with start/end times             | HubSpot Deals have pipeline stages; no native scheduling — captured as custom datetime properties                 |
| Invoices                      | Full invoice records with line items, tax, discounts, and payment status                           | HubSpot Deals hold total Amount; line items exist but invoice presentation requires rebuild or a third-party tool |
| Equipment / property tracking | Property Profiles store item type, make, model, serial, install date per customer address          | No native equipment object — requires a custom object with fields for type, make, model, serial                   |
| Employees                     | Employee records with name, phone, email, certifications                                           | HubSpot Users for licensed seats; employees not in the CRM can be stored as Contacts with a role property         |
| Price book                    | Price Book with services, materials, and price-form configurations                                 | No native price book — services map as line-item templates or custom properties on Deals                          |

## Housecall Pro to HubSpot field mapping

The 30 most-used fields of 49 mapped for this pair. Custom fields are added from your own schema during scoping. [Download the full mapping (CSV) ↓](https://flitstack.ai/migrations/crm/housecall-pro/to/hubspot.csv) or open it in the [field mapping template](https://flitstack.ai/tools/field-mapping-template).

******Field mapping 5 shown

Housecall Pro HubSpot

1. `first_name` Customer `firstname` Contact
2. `last_name` Customer `lastname` Contact
3. `email` Customer `email` Contact
4. `mobile_number` Customer `mobilephone` Contact
5. `home_number` Customer `phone` Contact

| Housecall Pro field              | HubSpot field                     | Mapping                 | Note                                                                                                                                                      |
| -------------------------------- | --------------------------------- | ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Customer.first_name`            | `Contact.firstname`               | direct                  |                                                                                                                                                           |
| `Customer.last_name`             | `Contact.lastname`                | direct                  |                                                                                                                                                           |
| `Customer.email`                 | `Contact.email`                   | direct                  |                                                                                                                                                           |
| `Customer.mobile_number`         | `Contact.mobilephone`             | direct                  |                                                                                                                                                           |
| `Customer.home_number`           | `Contact.phone`                   | direct                  |                                                                                                                                                           |
| `Customer.work_number`           | `Contact.office_phone`            | custom\_field\_required | HubSpot standard Contact has no dedicated work phone; stored as a custom property if needed.                                                              |
| `Customer.company`               | `Company.name`                    | direct                  |                                                                                                                                                           |
| `Customer.addresses[0].street`   | `Contact.address`                 | direct                  |                                                                                                                                                           |
| `Customer.addresses[0].city`     | `Contact.city`                    | direct                  |                                                                                                                                                           |
| `Customer.addresses[0].state`    | `Contact.state`                   | direct                  |                                                                                                                                                           |
| `Customer.addresses[0].zip`      | `Contact.zip`                     | direct                  |                                                                                                                                                           |
| `Customer.addresses[0].country`  | `Contact.country`                 | direct                  |                                                                                                                                                           |
| `Customer.notifications_enabled` | `Contact.hubspot_owner_id`        | direct                  | Used to flag notification opt-out status; stored as a custom boolean property.                                                                            |
| `Customer.tags`                  | `Contact.Tags__c`                 | custom\_field\_required | HubSpot Deal has no native tag model; HCP tags stored as comma-separated text in a custom property.                                                       |
| `Customer.lead_source`           | `Contact.hs_lead_status`          | direct                  |                                                                                                                                                           |
| `Customer.created_at`            | `Contact.Original_Create_Date__c` | custom\_field\_required | HubSpot CreatedDate is set at migration time; original HCP create date preserved in a custom datetime field.                                              |
| `Customer.id`                    | `Contact.HCP_Customer_ID__c`      | custom\_field\_required | HCP internal UUID stored for traceability, deduplication, and delta-run record matching.                                                                  |
| `Job.id`                         | `Deal.HCP_Job_ID__c`              | custom\_field\_required | HCP internal job UUID stored on the Deal for traceability and delta-run matching.                                                                         |
| `Job.customer_id`                | `Deal.associations.contact_id`    | direct                  | Job linked to HubSpot Contact by matching HCP customer ID to HCP\_Customer\_ID\_\_c.                                                                      |
| `Job.status`                     | `Deal.dealstage`                  | value\_mapping          | HCP statuses (scheduled, in\_progress, completed, cancelled, no\_access) map via value table to HubSpot deal stages. Mappings confirmed before migration. |
| `Job.job_type`                   | `Deal.HCP_Job_Type__c`            | custom\_field\_required | HubSpot has no native job-type field; each unique HCP Job Type becomes a pick-list value in HCP\_Job\_Type\_\_c.                                          |
| `Job.description`                | `Deal.description`                | direct                  |                                                                                                                                                           |
| `Job.notes`                      | `Deal.hs_note_body`               | direct                  |                                                                                                                                                           |
| `Job.address`                    | `Deal.address`                    | direct                  |                                                                                                                                                           |
| `Job.scheduled_start`            | `Deal.Job_Scheduled_Start__c`     | custom\_field\_required | HubSpot Deals have no native scheduling field; stored as a custom datetime property to preserve the service appointment window.                           |
| `Job.started_at`                 | `Deal.Job_Started_At__c`          | custom\_field\_required | Actual job start timestamp preserved as a custom datetime field on the Deal.                                                                              |
| `Job.employee_id`                | `Deal.hubspot_owner_id`           | transformed             | Owner resolved by email match to HubSpot users. Unmatched employees flagged before migration; fallback owner assigned per your rule.                      |
| `Job.subtotal`                   | `Deal.amount`                     | direct                  |                                                                                                                                                           |
| `Job.total`                      | `Deal.HCP_Total__c`               | custom\_field\_required | HCP total may include tax; stored separately from HubSpot Amount in a custom property.                                                                    |
| `Job.tax_amount`                 | `Deal.Tax_Amount__c`              | custom\_field\_required | HubSpot Deals have no native tax field; stored as a custom currency property alongside Amount.                                                            |

## What to watch for in a Housecall Pro to HubSpot migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

### HubSpot has no native Housecall Pro integration — no real-time sync without rebuilding

Housecall Pro and HubSpot do not share a native sync integration.

How we handle it

Teams that run both platforms today typically maintain them in parallel with manual exports or webhook middleware. After migration, your HubSpot account becomes the CRM of record. Any ongoing field-service data (new jobs, invoices, payment events) needs to be re-synced via a custom integration built on the Housecall Pro webhook API (available on MAX plans) and the HubSpot API. FlitStack does not maintain a live sync — it migrates historical data and leaves a documented webhook endpoint specification for your developers to implement a continuous feed if needed.

high

### Job status to deal-stage mapping requires manual value configuration before migration

Housecall Pro job statuses (scheduled, in\_progress, completed, cancelled, no\_access) have no automatic HubSpot equivalent — HubSpot deal stages are tenant-specific pick-lists that your admin defines per pipeline.

How we handle it

Before FlitStack runs the migration, your team must confirm the mapping table: which HCP status maps to which HubSpot deal stage name and probability. If you have multiple Housecall Pro pipelines, each may need its own HubSpot pipeline and stage configuration. FlitStack delivers the mapping plan before data lands and holds the migration until the stage configuration is confirmed in writing.

medium

### Property Profile equipment data requires HubSpot custom-object setup before migration

Housecall Pro Property Profiles track item type, make, model, serial number, and install date per customer address.

How we handle it

HubSpot has no native equipment or asset object in most tiers — the Equipment custom object must be created in HubSpot before migration, with fields for each data point and a lookup relationship to the Contact record. FlitStack delivers a custom-object schema specification during the planning phase. If you have more than 500 equipment records per customer, the migration run-list is partitioned to stay within HubSpot API batch limits.

medium

### HubSpot Deals do not function as invoices — invoice presentation must be rebuilt

Housecall Pro invoices carry full line-item detail, tax, discount, payment history, and status (paid, overdue, void).

How we handle it

HubSpot Deals store a single Amount field and have no native invoice PDF generation or payment history log. FlitStack migrates invoice totals, tax amounts, and payment status as Deal properties, but your team must rebuild invoice presentation — either using HubSpot's quote tool, a connected invoice app from the HubSpot App Marketplace, or a custom integration with your accounting software. This is a structural difference between a field-service billing platform and a CRM, not a data-loss issue.

low

### Employee records are not HubSpot Users by default — admin creates seat access manually

Housecall Pro employee records (name, email, phone, role) map to HubSpot Contacts with FlitStack, but HubSpot seat licenses require separate User creation in HubSpot's Settings.

How we handle it

If your technicians, dispatchers, or admin staff need HubSpot logins, your HubSpot admin creates their User accounts after migration and matches them by email to the migrated Contact records. FlitStack preserves the employee email in the migrated Contact so the match is straightforward. This is a HubSpot admin step — FlitStack cannot provision HubSpot User seats on your behalf.

## How the migration runs

1. ### Audit Housecall Pro data volume and configure HubSpot schema

   FlitStack pulls a data inventory from the Housecall Pro API covering customers, jobs, invoices, estimates, leads, employees, and Property Profiles.

   What this step covers

   We count records per object, identify unique job statuses, job types, and price-book entries, and surface any data-quality issues (duplicate emails, missing required fields). Simultaneously, we deliver the HubSpot custom-object schema specification for the Equipment object, the custom property setup for job\_type, tax, discount, and scheduled time, and the deal pipeline and stage configuration guide. Your HubSpot admin creates the schema before FlitStack begins field mapping.

2. ### Build the field-mapping specification and job-status value table

   FlitStack produces a field-mapping document covering every HCP field in this migration's scope.

   What this step covers

   The job-status-to-deal-stage value table is the critical path item — your team confirms which HCP statuses map to which HubSpot deal stages and pipeline. We also map Property Profile equipment fields to the HubSpot Equipment custom object, define the employee-to-contact mapping, and confirm which HubSpot users correspond to HCP employee IDs by email match. The specification is reviewed and signed off before any data moves.

3. ### Run a sample migration with field-level diff

   A representative slice migrates first — typically 100–500 records spanning customers, jobs, invoices, and a few Property Profile entries.

   What this step covers

   FlitStack generates a field-level diff showing source value versus destination value for every mapped field. You verify that job statuses landed in the correct deal stages, equipment records linked to the right contacts, and line items appear on estimate Deals. Sample results are reconciled against a manual spot-check in Housecall Pro before the full run is authorized.

4. ### Execute full migration with delta-pickup and audit log

   The full migration runs against HubSpot using the confirmed field-mapping specification.

   What this step covers

   A delta-pickup window of 24–48 hours runs after the initial load, capturing any records created or modified in Housecall Pro during the cutover. FlitStack's audit log records every operation — create, update, link — with source ID and destination ID. If reconciliation detects missing records or incorrect links, one-click rollback reverses the full load so the issue can be diagnosed and the run re-executed.

5. ### Deliver export package for manual rebuild and post-migration verification

   FlitStack delivers a structured export of your Housecall Pro workflow and automation definitions (visible via the API or UI export) as a reference document for rebuilding those in HubSpot.

   What this step covers

   Invoice presentation templates, payment reminder sequences, and customer notification rules are not migrated — they have no HubSpot equivalent and must be rebuilt in HubSpot's automation tools. Your team runs a final record-count verification against the Housecall Pro source data to confirm completeness before closing the migration.

![](https://flitstack.ai/platforms/housecall-pro.png) Housecall Pro ![](https://flitstack.ai/platforms/hubspot.svg) HubSpot

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · HubSpot Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**48–72 hours for under 50,000 records** Typical, smaller accounts

**5–7 days for over 500,000 records or multi-object custom schema setups** Large or heavily customised accounts

Housecall Pro to HubSpot migrations land in the lower-to-mid range of FlitStack's pricing because the standard objects map cleanly: Customers → Contacts, Jobs → Deals, Estimates → Deals with line items. The main cost drivers are the number of Property Profile records (which require custom-object schema setup in HubSpot before migration), the total line-item count across invoices and estimates, and whether your Housecall Pro setup uses multiple job types that need separate HubSpot custom properties. HubSpot's per-object property limits (200 for Deals, 500 for Contacts) rarely constrain HCP migrations since HCP itself has no custom fields. Setups with over 10,000 Property Profile records, heavy invoice histories, or custom price-book configurations fall toward the upper end of the range. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for Housecall Pro to HubSpot →](https://flitstack.ai/contact)

## Why teams move from Housecall Pro to HubSpot

- Housecall Pro pricing stacks up fast: Essentials at $189/month plus Sales Proposal ($40), Pipeline ($50), and HCP Voice ($49) hits $328/month before payment processing at 2.59%+. Users report the base plan lacks expense tracking and robust reporting, making HubSpot's unified CRM and marketing suite a cost-consolidation play.
- Users report Housecall Pro lags with large customer databases — one reviewer noted five-minute delays finding records when their system grew beyond 10,000 customers. The platform's field-service optimization layer creates indexing overhead that compounds at scale. HubSpot's CRM architecture is engineered for large datasets and scales without the performance degradation seen in Housecall Pro's operational model.
- Housecall Pro has no native CRM for marketing automation or lead nurturing. Teams running HubSpot alongside HCP for marketing campaigns end up with duplicated records, manual sync, and conflicting customer views across both platforms. This split-brain scenario creates data silos and inconsistent customer engagement — a full migration consolidates your data into a single system of record, eliminating redundant entry and aligning your marketing, sales, and service operations.
- The reporting system in Housecall Pro draws consistent criticism: one reviewer noted it cannot report total gross sales by month or year, and internal QuickBooks sync breaks without explanation. HubSpot's reporting and analytics tools handle revenue attribution, deal velocity, and pipeline forecasting natively.

Questions, answered

## Housecall Pro to HubSpot migration questions

How long does a Housecall Pro to HubSpot migration take?

Most Housecall Pro to HubSpot migrations complete in 48–72 hours for under 50,000 records. The longest step is the planning phase — confirming job-status-to-deal-stage mappings and creating the HubSpot Equipment custom object — which runs in parallel with FlitStack's data audit. Larger setups with over 500,000 records, heavy Property Profile volume, or multi-pipeline job type configurations extend to 5–7 days. HubSpot API rate limits and batch sizing are the primary clock-time constraints on large-volume runs.

Will my Housecall Pro workflows and automations migrate to HubSpot?

No. FlitStack migrates data and schema only — workflows, job scheduling rules, automated customer notifications, and payment reminder sequences do not transfer. Housecall Pro's automation layer is built on its own field-service logic with no HubSpot equivalent. We can export your Housecall Pro workflow definitions as a structured reference document for your HubSpot admin to use when rebuilding those automations in HubSpot's workflow builder or a connected automation tool.

What happens to Housecall Pro job statuses in HubSpot?

Housecall Pro job statuses (scheduled, in\_progress, completed, cancelled, no\_access) map to HubSpot deal stages via a value-mapping table your team confirms before migration. The mapping is flexible — your admin defines the HubSpot pipeline and stage names, then FlitStack maps each HCP status to the corresponding stage. Job scheduled start and end times are stored as custom datetime properties on the Deal since HubSpot has no native scheduling field. A custom HCP\_Job\_Type\_\_c property preserves the original job type label from Housecall Pro.

Can I migrate Housecall Pro Property Profile equipment data to HubSpot?

Yes, but it requires a HubSpot custom object. Housecall Pro Property Profiles (item type, make, model, serial number, install date) have no native HubSpot equivalent. FlitStack creates an Equipment custom object in HubSpot with fields for each data point and links each equipment record to the corresponding Customer Contact via a lookup relationship. Multi-item properties per address generate multiple Equipment records. Your HubSpot admin confirms the custom-object schema before migration runs.

What happens to Housecall Pro invoices in HubSpot?

Housecall Pro invoices migrate as HubSpot Deals with the invoice total as the Deal amount, tax and discount stored as custom currency properties, and payment status (paid, partially paid, overdue, void) as a custom pick-list property. Line-item detail from the HCP invoice migrates to Deal line items. Note that HubSpot Deals are not formatted invoices — HubSpot has no native invoice PDF generation or payment history log. Your team rebuilds invoice presentation using HubSpot's quote tool, a connected app from the HubSpot App Marketplace, or a custom integration with your accounting software.

Does the migration affect my Housecall Pro account during cutover?

No. FlitStack uses read-only API access to Housecall Pro — your team continues working in Housecall Pro throughout the migration. No records are modified, deleted, or locked in Housecall Pro during the cutover. A delta-pickup window of 24–48 hours captures any new or modified customers, jobs, and invoices created in Housecall Pro during the migration run so the final HubSpot state reflects Housecall Pro's complete dataset at go-live.

How do I handle ongoing field-service data sync after the migration?

Housecall Pro and HubSpot do not have a native integration. After FlitStack migrates your historical data, any ongoing field-service activity (new jobs, invoice payments, updated customer records) needs a custom sync built on the Housecall Pro webhook API (available on MAX plans) and the HubSpot API. FlitStack delivers a webhook endpoint specification and data-contract document during the post-migration handoff so your developers can implement a continuous feed if you want to keep HubSpot updated as the system of record. Without a custom sync, HubSpot reflects the migrated snapshot and Housecall Pro remains the live operational system.

What does Housecall Pro's employee roster become in HubSpot?

Housecall Pro employees map to HubSpot Contacts with a custom role property marking them as staff. FlitStack preserves the name, email, phone, and role from HCP. If employees need HubSpot seat licenses — for your dispatchers, admins, or sales staff who will work in HubSpot — your HubSpot admin creates User accounts manually after migration and matches them by email to the migrated Contact records. HCP employee certifications and documents attach as files to the Contact record during migration.

## Related migrations

[![](https://flitstack.ai/platforms-trim/hubspot.webp) Migrate to **HubSpot** Every source we move into HubSpot, native options and the checklist. Guide, checklist & sources](https://flitstack.ai/migrations/crm/hubspot)

### [HubSpot implementation](https://flitstack.ai/services/hubspot-implementation)

[Set up HubSpot and migrate into it as one engagement.](https://flitstack.ai/services/hubspot-implementation)

[See the service →](https://flitstack.ai/services/hubspot-implementation) [**Convertkit to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/convertkit/to/hubspot) [**improveit 360 to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/improveit-360/to/hubspot) [**Gold-Vision to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/gold-vision/to/hubspot) [**Nutshell to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/nutshell/to/hubspot) [**Follow Up Boss to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/follow-up-boss/to/hubspot) [**Vinsolutions to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/vinsolutions/to/hubspot) [**Housecall Pro to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/housecall-pro/to/salesforce-sales-cloud) [**Housecall Pro to Pipedrive** Mapping · history · rollback](https://flitstack.ai/migrations/crm/housecall-pro/to/pipedrive) [**Housecall Pro to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/housecall-pro/to/dynamics-365-sales)

## Sources: official documentation

1. [Format import files — HubSpot Knowledge Base](https://knowledge.hubspot.com/import-and-export/set-up-your-import-file)
2. [Create and edit custom objects — HubSpot Knowledge Base](https://knowledge.hubspot.com/object-settings/create-custom-objects)
3. [Import objects programmatically — HubSpot Knowledge Base](https://knowledge.hubspot.com/import-and-export/import-objects)
4. [Understand property field types in HubSpot](https://knowledge.hubspot.com/properties/property-field-types-in-hubspot)
5. [Associate records on CRM objects — HubSpot Knowledge Base](https://knowledge.hubspot.com/records/associate-records)
6. [Integration throughput and limits — HubSpot Knowledge Base](https://knowledge.hubspot.com/integrations/integration-throughput-and-limits)
7. [HubSpot Cloud Infrastructure and Data Hosting FAQ](https://knowledge.hubspot.com/account-security/hubspot-cloud-infrastructure-and-data-hosting-frequently-asked-questions)

Get a quote

## Moving from Housecall Pro to HubSpot?

Tell us roughly how many records and objects you have. We scope the mapping and the HubSpot setup with you, then send a quote.

[Get a quote](https://flitstack.ai/contact)
