---
title: "Housecall Pro to Salesforce Migration | FlitStack AI"
description: "Migrate Housecall Pro to Salesforce 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/salesforce-sales-cloud"
---

# Housecall Pro to Salesforce migration

Moving from Housecall Pro to Salesforce Sales Cloud means translating a field service management data model into a CRM designed for sales cycles. FlitStack AI maps every customer, job, estimate, and property profile into Salesforce Accounts, Opportunities, and custom Job\_\_c objects — preserving original timestamps, technician assignments, and pricing data so your Salesforce reports reflect the full operational history from day one.

Short answer

FlitStack AI migrates account + contacts, account address fields + service\_location\_\_cs, job\_equipment\_\_cs, job\_\_cs and opportunities from Housecall Pro to Salesforce, 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 (customers, jobs, invoices, price book entries combined)..

![](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/salesforce-sales-cloud#field-mapping)

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

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

Destination Salesforce ![](https://flitstack.ai/platforms-trim/salesforce-sales-cloud.webp)

Account + Contact Account Address Fields + Service\_Location\_\_c Job\_Equipment\_\_c Job\_\_c Opportunity

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

## What moves from Housecall Pro to Salesforce?

Housecall Pro organizes home service operations around Jobs, Customers, Property Profiles, Estimates, Invoices, and a Price Book — each with its own API endpoint.

Read the full summary

Salesforce Sales Cloud uses a fundamentally different object model: Accounts, Contacts, Leads, Opportunities, and Cases. There is no native Job object in Salesforce, so FlitStack creates a custom Job\_\_c object to carry Housecall Pro job records with all their FSM-specific fields. The migration extracts Housecall Pro data via the REST API (Customers, Jobs, Estimates, Invoices, Price Book, Property Profiles, and Tags), transforms each record to match Salesforce conventions (AccountId lookups, Opportunity Contact Roles, RecordTypeId assignments), and loads via the Salesforce Bulk API. Scheduling windows become Events with custom technician and route fields. Property Profile equipment lists (A/C make, model, serial number) migrate as custom Job\_Equipment\_\_c records. The Price Book becomes a custom Price\_Book\_\_c object with Price\_Book\_Entry\_\_c children. Automations, routing logic, and SMS/notification templates built in Housecall Pro do not have Salesforce equivalents and must be rebuilt in Salesforce Flow. We provide an automation-export deliverable as a rebuild reference. Delta-pickup captures any Housecall Pro records modified during the cutover window.

direct

### Customer → Account + Contact

Housecall Pro Customers map directly to Salesforce Accounts.

How it maps

The primary address becomes the Account billing/service address. Contact fields (name, email, phone) sit on the related Contact record. Sub-customers in Housecall Pro become child Accounts with ParentId linking to the parent Account.

transformed

### Customer address → Account Address Fields + Service\_Location\_\_c

Housecall Pro allows multiple addresses per customer, separating billing and service locations.

How it maps

Salesforce Accounts can store only one primary address. FlitStack maps the primary service address to the standard Account fields and creates Service\_Location\_\_c junction records for any additional addresses. Each Service\_Location\_\_c record retains the address type, street, city, state, zip, and links to the parent Account via AccountId, preserving the original role from Housecall Pro.

custom\_field\_required

### Property Profile → Job\_Equipment\_\_c (custom object)

Housecall Pro Property Profile stores equipment lists per address (A/C type, make, model, serial number, install date).

How it maps

Salesforce has no native equivalent. FlitStack creates a Job\_Equipment\_\_c custom object linked to the Account's service address, preserving item type, make, model, serial number, and install date fields.

custom\_field\_required

### Job → Job\_\_c (custom object)

Housecall Pro Jobs are the core FSM record — they have no Salesforce equivalent.

How it maps

FlitStack creates a Job\_\_c custom object with fields for job status, job type, scheduled date, technician, route ID, service address, customer reference, and pricing. Job\_\_c links to the Account via AccountId.

merged

### Job → Opportunity

Housecall Pro Jobs that generate revenue—whether invoiced or estimated—also flow into Salesforce Opportunities for pipeline reporting.

How it maps

The Opportunity captures the monetary amount, sales stage, and expected close date from the job, while Job\_\_c remains the FSM record of truth. FlitStack maps job amount to Opportunity.Amount, translates job status to a stage value, and records the close date from the job’s scheduled completion.

custom\_field\_required

### Estimate → Estimate\_\_c (custom object)

Housecall Pro Estimates are customer-facing proposals that have no direct counterpart in Salesforce's standard objects.

How it maps

FlitStack creates a custom Estimate\_\_c object to store each estimate, including fields for the total amount, status (Draft, Sent, Accepted, Declined), the linked Account, and a reference to the associated Job\_\_c. This allows the sales team to track estimate history and conversion rates directly within Salesforce, while preserving the original estimate data from Housecall Pro.

******What moves 12 objects

Housecall Pro Salesforce

- Customer Account 1:1
- Customer address Account Address Fields transformed
- Property Profile Job\_Equipment\_\_c transformed
- Job Job\_\_c transformed
- Job Opportunity merged
- Estimate Estimate\_\_c transformed

\+ 6 more in the mapping below

## How Housecall Pro and Salesforce 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                                                                                                                                                                                   | Salesforce                                                                                                                                                                                                   |
| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Core object model             | Housecall Pro organizes around Customers, Jobs, Property Profiles, and Estimates — all via separate API endpoints (GET /customers, GET /jobs, GET /price-book). No native CRM concept of Leads. | Salesforce Sales Cloud organizes around Accounts, Contacts, Leads, Opportunities, and Cases. There is no native Job or Estimate object — FSM data requires custom Job\_\_c and custom Estimate\_\_c objects. |
| Scheduling / routing          | Housecall Pro uses Job Appointments and Routes to assign technicians to time windows. GET /appointments and GET /routes expose this natively.                                                   | Salesforce Events model calendar time but do not carry technician-route groupings. FlitStack maps Route IDs to custom Route\_\_c lookups on Event records.                                                   |
| Equipment / property tracking | Property Profile stores equipment lists per address: item type (A/C, heater), make, model, serial number, install date. Unique to Housecall Pro FSM model.                                      | Salesforce has Asset objects for product tracking, but no native per-address equipment list. FlitStack creates custom Job\_Equipment\_\_c records linked to the job's service address Account.               |
| Price book                    | Housecall Pro Price Book (GET /price-book) holds services, materials, and flat-rate pricing. Line items on estimates reference these.                                                           | Salesforce Pricebook2 is standard but tied to Opportunities with OpportunityLineItems. Housecall Pro flat-rate services require custom Price\_Book\_\_c + custom Price\_Book\_Entry\_\_c objects.            |
| Custom fields                 | Housecall Pro does not support custom fields on customers, jobs, or invoices — only a custom message on invoice templates. No \_\_c equivalent.                                                 | Salesforce relies heavily on custom fields (API suffix \_\_c) for domain-specific data. All Housecall Pro FSM properties migrate as Salesforce custom fields on Job\_\_c.                                    |
| Job status lifecycle          | Housecall Pro job status follows: Scheduled → In Progress → Completed / Cancelled / No Show. Four-state FSM lifecycle.                                                                          | Salesforce Opportunity StageName is a pick-list tied to Sales Processes and Record Types. FlitStack maps each Housecall Pro status to a custom Job\_Status\_\_c pick-list on Job\_\_c.                       |
| Automation / routing rules    | Housecall Pro automations handle SMS reminders, payment triggers, and route assignments. No public workflow export API.                                                                         | Salesforce Flow handles all automation. FlitStack does NOT migrate automations — we export Housecall Pro workflow definitions as a reference document for Salesforce-side rebuild.                           |
| Customer hierarchy            | Housecall Pro supports sub-customers (child accounts) for billing but not native parent-child CRM hierarchy on customer records.                                                                | Salesforce Account model supports ParentId for hierarchical company structures. Sub-customers migrate as child Accounts with ParentId linking.                                                               |

## Housecall Pro to Salesforce field mapping

The 30 most-used fields of 52 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/salesforce-sales-cloud.csv) or open it in the [field mapping template](https://flitstack.ai/tools/field-mapping-template).

******Field mapping 5 shown

Housecall Pro Salesforce

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      | Salesforce 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.company`       | `Account.Name`                    | direct                  |                                                                                                                                                           |
| `Customer.notes`         | `Contact.Description`             | direct                  |                                                                                                                                                           |
| `Customer.tags`          | `Contact.Customer_Tags__c`        | custom\_field\_required | Housecall Pro tags stored as a multi-select custom pick-list on Contact.                                                                                  |
| `Customer.lead_source`   | `Contact.LeadSource`              | direct                  |                                                                                                                                                           |
| `Customer.created_at`    | `Contact.Original_Create_Date__c` | custom\_field\_required | Salesforce CreatedDate reflects migration time. Original Housecall Pro timestamp preserved as custom datetime field.                                      |
| `Customer.id`            | `Contact.Source_System_ID__c`     | custom\_field\_required | Housecall Pro internal ID stored for traceability and delta-run de-duplication.                                                                           |
| `Job.id`                 | `Job__c.Source_System_ID__c`      | custom\_field\_required | Housecall Pro job ID stored for traceability and delta-run de-duplication.                                                                                |
| `Job.status`             | `Job__c.Job_Status__c`            | value\_mapping          | Housecall Pro status values (Scheduled, In Progress, Completed, Cancelled, No Show) map to custom pick-list on Job\_\_c. No native Salesforce equivalent. |
| `Job.job_type`           | `Job__c.Job_Type__c`              | custom\_field\_required | Housecall Pro job types (e.g., HVAC Repair, Plumbing, Electrical) stored as custom pick-list on Job\_\_c, mapped to RecordTypeId for segmentation.        |
| `Job.scheduled_date`     | `Event.StartDateTime`             | direct                  |                                                                                                                                                           |
| `Job.scheduled_date`     | `Job__c.Scheduled_Date__c`        | direct                  |                                                                                                                                                           |
| `Job.technician_id`      | `Event.OwnerId`                   | transformed             | Technician resolved by email match to Salesforce User. FlitStack flags unmatched technicians before migration.                                            |
| `Job.technician_id`      | `Job__c.Technician__c`            | custom\_field\_required | Custom lookup to User storing the assigned technician name from Housecall Pro.                                                                            |
| `Job.route_id`           | `Event.Route_ID__c`               | custom\_field\_required | Housecall Pro route grouping preserved as custom text field on the Event record.                                                                          |
| `Job.customer_id`        | `Job__c.AccountId`                | transformed             | Job linked to the migrated Account record via AccountId lookup.                                                                                           |
| `Job.address`            | `Job__c.Service_Address__c`       | custom\_field\_required | Housecall Pro job service address stored as custom text field on Job\_\_c, matching the service address on the Account.                                   |
| `Job.total_price`        | `Job__c.Job_Amount__c`            | direct                  |                                                                                                                                                           |
| `Job.total_price`        | `Opportunity.Amount`              | merged                  | Job revenue merges into the related Opportunity for pipeline reporting.                                                                                   |
| `Job.customer_notes`     | `Job__c.Customer_Notes__c`        | direct                  |                                                                                                                                                           |
| `Job.private_notes`      | `Job__c.Private_Notes__c`         | direct                  |                                                                                                                                                           |
| `Job.created_at`         | `Job__c.Original_Create_Date__c`  | custom\_field\_required | Original Housecall Pro job creation timestamp preserved for historical reporting continuity.                                                              |
| `Estimate.id`            | `Estimate__c.Source_System_ID__c` | custom\_field\_required | Housecall Pro estimate ID stored for traceability.                                                                                                        |
| `Estimate.status`        | `Estimate__c.Estimate_Status__c`  | value\_mapping          | Housecall Pro estimate statuses (Draft, Sent, Accepted, Declined) mapped to custom pick-list.                                                             |
| `Estimate.total_price`   | `Estimate__c.Amount__c`           | direct                  |                                                                                                                                                           |
| `Estimate.customer_id`   | `Estimate__c.AccountId`           | transformed             | Estimate linked to migrated Account by Housecall Pro customer\_id.                                                                                        |

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

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

high

### Job\_\_c custom object required — no native Salesforce equivalent

Housecall Pro Jobs are the atomic unit of field service operations, holding status, scheduled date, technician assignment, pricing, and customer notes.

How we handle it

Salesforce has no Job object — the standard model uses Opportunities for revenue-bearing work and Cases for service requests, but neither captures FSM-specific fields like technician assignment, route ID, or job type. FlitStack creates a Job\_\_c custom object with all FSM-specific fields as custom fields, and merges revenue data into Opportunities for pipeline reporting. This requires Salesforce admin setup of the Job\_\_c object schema before data loads. The custom object must be deployed to your Salesforce org before migration runs.

high

### Property Profile equipment lists require Job\_Equipment\_\_c custom object

Housecall Pro Property Profiles store equipment lists per service address — item type (A/C, heater, water heater), make, model, serial number, and install date.

How we handle it

This is a core data model in Housecall Pro's FSM offering. Salesforce has no native per-address equipment list. Asset objects track products installed at accounts but do not support the multi-item, per-address equipment profile that Housecall Pro uses. FlitStack creates a Job\_Equipment\_\_c custom object with a master-detail relationship to Job\_\_c, storing each piece of equipment as a separate record with all Housecall Pro fields preserved. Your Salesforce admin must deploy this object before migration.

high

### Housecall Pro Price Book flat-rate services don't map to Salesforce standard Pricebook2

Housecall Pro's Price Book holds services, materials, and flat-rate pricing that technicians apply to jobs.

How we handle it

Salesforce's standard Pricebook2 model is built for OpportunityLineItems tied to Products with list prices — it does not natively support flat-rate service entries without a Product record. Housecall Pro price book entries with flat rates, cost-plus pricing, or per-trip charges require a custom Price\_Book\_\_c object with Price\_Book\_Entry\_\_c children. If your price book has more than 200 line items, the custom object chain adds significant validation complexity. FlitStack delivers the full price-book translation plan before the migration runs so your admin can pre-create the custom objects.

medium

### Housecall Pro automations (SMS, payment triggers, routing) do not migrate — no export API

Housecall Pro's automation features — SMS customer reminders, payment processing triggers, auto-assignment rules, and routing logic — have no Salesforce equivalent and no public export API.

How we handle it

FlitStack migrates data and schema only. The automation export deliverable is limited to screenshots and configuration notes from within Housecall Pro's UI; it is not a machine-readable migration artifact. Your Salesforce admin will need to rebuild automations in Flow using these notes as a reference. This is a material planning item for teams that rely heavily on Housecall Pro's automated workflows.

medium

### Job status values require custom pick-list mapping — no native Housecall Pro status equivalent in Salesforce

Housecall Pro job statuses (Scheduled, In Progress, Completed, Cancelled, No Show) are a four-state FSM lifecycle.

How we handle it

Salesforce Opportunity StageName is a sales-stage pick-list tied to Sales Processes and Record Types, not an FSM job lifecycle. Mapping Housecall Pro statuses directly to Opportunity stages creates confusion in reporting because the stage probabilities and forecast categories are designed for sales pipelines. FlitStack creates a custom Job\_Status\_\_c pick-list on Job\_\_c with Housecall Pro's exact status values preserved, then surfaces the status in Salesforce reports via the Job\_\_c object. This keeps the FSM lifecycle intact without distorting Salesforce's sales forecasting model.

## How the migration runs

1. ### Extract Housecall Pro data via REST API

   FlitStack connects to Housecall Pro using API key authentication (MAX plan required) and exports all objects: Customers, Jobs, Estimates, Invoices, Price Book, Property Profiles, Employees, Leads, and Tags.

   What this step covers

   Each object is pulled via its dedicated endpoint (GET /customers, GET /jobs, GET /price-book, etc.). We capture created\_at and updated\_at timestamps for every record to enable delta-pickup during the cutover window. If your Housecall Pro plan does not include API access, we work with the data export available on MAX plans or advise on upgrading before migration.

2. ### Design Salesforce custom object schema

   Based on the Housecall Pro data inventory, FlitStack delivers a Salesforce schema design document specifying: the Job\_\_c custom object with all FSM fields, Job\_Equipment\_\_c as a child of Job\_\_c, Estimate\_\_c linked to Job\_\_c, Price\_Book\_\_c with Price\_Book\_Entry\_\_c children, and all custom fields needed on standard objects.

   What this step covers

   The document includes API field names, pick-list values, data types, and which fields map to existing Salesforce standard fields vs. custom fields. Your Salesforce admin creates the schema in your sandbox first; FlitStack validates it before the migration dry run.

3. ### Map and transform all records in staging

   All Housecall Pro records are mapped to Salesforce objects: Customers → Accounts + Contacts, Jobs → Job\_\_c + Opportunity (for revenue), Property Profiles → Job\_Equipment\_\_c, Estimates → Estimate\_\_c, Price Book → Price\_Book\_\_c + Price\_Book\_Entry\_\_c.

   What this step covers

   Technician email addresses are resolved to Salesforce User IDs. Sub-customers receive ParentId linking. Job status values are translated via the value-mapping table to the custom Job\_Status\_\_c pick-list. Records that cannot be matched (unresolved technicians, orphaned addresses) are flagged in a pre-migration exception report.

4. ### Run sample migration with field-level diff

   A representative slice migrates first — typically 100–500 records spanning customers, jobs, estimates, and price book entries.

   What this step covers

   FlitStack generates a field-level diff between the Housecall Pro source record and the Salesforce destination record so you can verify: that technician assignment is correct, that property profile equipment lists are fully populated in Job\_Equipment\_\_c, that estimate status and amounts match, and that price book entries are correctly structured. You approve the sample before the full migration commits.

5. ### Execute full migration with delta-pickup

   The full migration loads via the Salesforce Bulk API in batches.

   What this step covers

   A delta-pickup window (typically 24–48 hours) runs in parallel, capturing any Housecall Pro records created or modified during the cutover. FlitStack generates a reconciliation report comparing record counts and field totals between Housecall Pro and Salesforce. If reconciliation fails, one-click rollback reverts the Salesforce org to its pre-migration state. The automation-export reference document is delivered alongside the migration completion report.

![](https://flitstack.ai/platforms/housecall-pro.png) Housecall Pro ![](https://flitstack.ai/platforms/salesforce-sales-cloud.svg) Salesforce

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 · Salesforce 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 (customers, jobs, invoices, price book entries combined).** Typical, smaller accounts

**5–7 days for over 500,000 records or complex custom object / price-book setups requiring per-line-item mapping.** Large or heavily customised accounts

A quote scales with three drivers: total record volume across all Housecall Pro objects (customers, jobs, invoices, price book entries, property profiles), the number of custom Salesforce fields required to capture FSM-specific data (Job\_Status\_\_c, Technician\_\_c, Route\_ID\_\_c, Job\_Type\_\_c), and the complexity of the price-book translation (flat-rate services in Housecall Pro require custom Price\_Book\_\_c + Price\_Book\_Entry\_\_c setup in Salesforce). Housecall Pro setups with more than 200 line items in the price book or multiple property profiles per customer fall into the upper price range because the Job\_Equipment\_\_c and price-book object chains increase mapping and validation work significantly. Every quote is scoped with you; there is no self-serve pricing.

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

## Why teams move from Housecall Pro to Salesforce

- Housecall Pro pricing tiers bundle essential features behind add-on modules — the Sales Proposal ($40/mo), Pipeline ($50/mo), and HCP Voice ($49/mo) packages inflate the effective monthly cost well beyond $300/mo for growing field service businesses that require only basic CRM functionality in Salesforce. In addition, tier upgrades often come with limited API call caps, forcing extra spending on higher-tier plans to maintain data integration.
- Performance lag and recurring bugs when managing multiple simultaneous jobs create frustration for field service crews during peak season periods. On G2, users consistently report system slowdowns when making real-time updates to job status, technician assignments, or customer notes. These reliability issues can delay dispatch decisions and reduce overall crew productivity, whereas Salesforce Sales Cloud maintains consistent response times even under heavy transactional loads.
- Housecall Pro lacks native map-based scheduling with drag-and-drop route optimization. Reviewers specifically call out that the scheduler does not show geographic job locations, forcing dispatchers to mentally route technicians — a gap Salesforce Field Service or third-party routing tools close.
- Home service companies that expand their operations to require enterprise-level reporting, multi-location management, and tight integrations with ERP or accounting platforms quickly outgrow Housecall Pro's limited reporting tools and API capabilities. As business complexity increases, the need for deeper data analysis, cross-location dashboards, and real-time financial feeds becomes critical. Salesforce addresses this with its extensive AppExchange marketplace of over 5,000 applications and built-in Analytics Cloud, delivering a richer data layer and more flexible reporting options.
- When a field service company is acquired by or merges with an organization already operating on Salesforce Sales Cloud, migrating Housecall Pro data into the parent company's CRM eliminates the cost and complexity of maintaining two separate platforms. This consolidation reduces licensing fees, simplifies data governance, and enables the combined team to leverage a unified customer view and standardized reporting across all locations.

Questions, answered

## Housecall Pro to Salesforce migration questions

How long does a Housecall Pro to Salesforce Sales Cloud migration take?

Most Housecall Pro to Salesforce migrations complete in 48–72 hours of clock time for under 50,000 combined records across customers, jobs, estimates, and price book entries. Larger setups with 500,000+ records or complex price-book structures (200+ line items) extend to 5–7 days. The longest planning step is designing the Salesforce custom object schema (Job\_\_c, Job\_Equipment\_\_c, Price\_Book\_\_c) — FlitStack delivers this as a design document so your admin can pre-build it before migration runs.

Will my Housecall Pro automations migrate to Salesforce Flow?

No. FlitStack AI migrates data and schema only — automations, SMS reminders, payment triggers, routing rules, and auto-assignment logic in Housecall Pro do not migrate. There is no public API to export Housecall Pro automation configurations as machine-readable artifacts. We can provide screenshots and configuration notes from within Housecall Pro's UI as a rebuild reference for your Salesforce admin. SMS customer notifications, payment processing triggers, and routing logic must be rebuilt in Salesforce Flow, Flow Builder, or Apex.

What does a Housecall Pro Job become in Salesforce?

A Housecall Pro Job maps to two Salesforce objects: a custom Job\_\_c record holding all FSM-specific fields (status, job type, technician, route ID, scheduled date, pricing, notes), and an Opportunity record capturing the revenue amount and close date for pipeline reporting. The Job\_\_c object is the FSM-of-record; the Opportunity provides the CRM pipeline view. Housecall Pro job status values (Scheduled, In Progress, Completed, Cancelled, No Show) migrate as a custom Job\_Status\_\_c pick-list since Salesforce has no native FSM job lifecycle equivalent.

Can I migrate Housecall Pro Property Profiles to Salesforce?

Yes, but not to a native Salesforce object. Property Profiles (equipment lists per address: A/C type, make, model, serial number, install date) have no Salesforce equivalent — the standard Asset object tracks products but not multi-item per-address equipment lists. FlitStack creates a custom Job\_Equipment\_\_c object with a master-detail relationship to Job\_\_c, storing each piece of equipment as a separate record. Your Salesforce admin deploys the Job\_Equipment\_\_c object schema before migration. Equipment associations to specific service addresses link via the AccountId on the related Job\_\_c record.

Does the migration affect my Housecall Pro account during the cutover?

No. FlitStack AI uses scoped read access on Housecall Pro via API key — your team keeps working in Housecall Pro throughout the migration. The delta-pickup window (24–48 hours) runs after the full migration completes, capturing any customers, jobs, or estimates modified in Housecall Pro during the cutover. Records created or updated after the delta window closes are not captured by the migration but can be manually re-synced or migrated in a follow-up session. No data is deleted from Housecall Pro during the migration process.

What happens to Housecall Pro estimates and pending quotes after migration?

Housecall Pro Estimates migrate as custom Estimate\_\_c records linked to the migrated Account and Job\_\_c. The estimate status (Draft, Sent, Accepted, Declined) maps to a custom Estimate\_Status\_\_c pick-list. Accepted estimates that have not yet been converted to invoices require manual follow-up — FlitStack generates an Open\_Estimates\_\_c report listing all Estimate\_\_c records with status 'Sent' or 'Draft' so your team can follow up with customers. Invoices in Housecall Pro migrate as Opportunity-level custom fields capturing amount and payment status, not as separate Salesforce invoice objects.

How does Housecall Pro technician and employee data become Salesforce Users?

Housecall Pro employees and technicians map to Salesforce Users by email match. The Housecall Pro employee email field is matched against Salesforce User Email. Matched employees receive their Housecall Pro role as a custom Role\_\_c field on User and their certification data in a custom Certifications\_\_c field. Unmatched employees are flagged in a pre-migration exception report — your team either creates Salesforce Users for them before migration or assigns their jobs to a fallback owner. FlitStack does not auto-provision Salesforce users; that requires admin action in your Salesforce org.

## Related migrations

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

### [Salesforce implementation](https://flitstack.ai/services/salesforce-implementation)

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

[See the service →](https://flitstack.ai/services/salesforce-implementation) [**Daylite to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/daylite/to/salesforce-sales-cloud) [**Convertkit to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/convertkit/to/salesforce-sales-cloud) [**Copper to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/copper/to/salesforce-sales-cloud) [**FotoNotes to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/fotonotes/to/salesforce-sales-cloud) [**HoneyBook to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/honeybook/to/salesforce-sales-cloud) [**Customer.io to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/customer-io/to/salesforce-sales-cloud) [**Housecall Pro to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/housecall-pro/to/hubspot) [**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. [Custom Field Attributes — Salesforce Help (External ID)](https://help.salesforce.com/s/articleView?id=platform.custom_field_attributes.htm)
2. [Increase Limit of Salesforce Big Object Storage Allocation — Salesforce Help](https://help.salesforce.com/s/articleView?id=000380434\&type=1)
3. [Uploading Activity data to Salesforce — Salesforce Stack Exchange](https://salesforce.stackexchange.com/questions/15694/uploading-activity-data-to-salesforce)
4. [Sandboxes — Staging Environments for Customizing and Testing](https://resources.docs.salesforce.com/latest/latest/en-us/sfdc/pdf/deploy_sandboxes.pdf)
5. [Case Comment STRING\_TOO\_LONG — Salesforce Stack Exchange](https://salesforce.stackexchange.com/questions/44763/case-comment-error-string-too-long-body-data-value-too-large)
6. [Salesforce Data Migration: 7 Challenges and How to Solve Them — DEV](https://dev.to/prince_6a5fbc059971cef8c8/salesforce-data-migration-7-challenges-and-how-to-solve-them-3bb7)
7. [Salesforce Duplicate Management — Salesforce Stack Exchange](https://salesforce.stackexchange.com/questions/151012/salesforce-duplicate-management-importing-duplicates)

Get a quote

## Moving from Housecall Pro to Salesforce?

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

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