Skip to content
Get a quote

Housecall Pro to Dynamics 365 migration

Migrating from Housecall Pro to Dynamics 365 Sales moves your home-service operation into Microsoft's CRM ecosystem with Copilot AI insights and native Office 365 integration. FlitStack AI maps every customer, job history, property profile, estimate, and invoice — translating Housecall Pro's job-and-estimate model into Dynamics 365 Sales opportunities, quotes, and custom entities. Your price book becomes the Dynamics 365 product catalog. Workflows, automations, and third-party integrations require separate rebuilds in D365 Sales or Power Automate.

Short answer

FlitStack AI migrates contacts, account + contacts, opportunity + activities, quotes and invoices from Housecall Pro to Dynamics 365, 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.

By

Source Housecall Pro
DestinationDynamics 365
ContactAccount + ContactOpportunity + ActivitiesQuoteInvoice
Mapped field by field · sample run · one-click rollback

What moves from Housecall Pro to Dynamics 365?

Housecall Pro is purpose-built for field-service operations — flat customers, jobs as the primary work record, estimates, invoices, and a price book for services.

Read the full summary

Dynamics 365 Sales is a general-purpose CRM built around leads, opportunities, quotes, and a product catalog, with Account-Contact hierarchies and pipeline stages. When operations grow beyond single-location scheduling into multi-entity relationship management, the flat Housecall Pro customer model becomes a constraint — Dynamics 365 Sales handles Account hierarchies, territory management, and AI-driven pipeline forecasting that Housecall Pro does not provide. FlitStack AI maps Housecall Pro customers to Contacts (or Accounts for commercial customers), jobs to Opportunities with their associated activities, estimates to Quotes, and invoices to D365 invoice records. Property profiles (equipment make, model, serial number) become custom fields on the Contact or a custom Equipment entity. The price book translates to the Dynamics 365 product catalog with price list entries. We preserve source system IDs for delta-run de-duplication and preserve original create dates as custom datetime fields. Workflows, automations, job-dispatch rules, reporting dashboards, and third-party integrations do not migrate — those are destination-side schema configuration that must be rebuilt in D365 Sales or Power Automate after the data lands. A sample migration with field-level diff runs first so you verify mapping accuracy before the full cutover commits.

direct

Customer → Contact

Housecall Pro customers map 1:1 to Dynamics 365 Contacts.

How it maps

All contact fields (first name, last name, email, phone, mobile, addresses) map directly. For commercial customers with multiple contacts, we create an Account first and link all related Contacts to it. Tags and custom notes on the customer record migrate to custom fields on Contact.

transformed

Customer (commercial) → Account + Contact

When a Housecall Pro customer has a company name and multiple employees or locations, we create a D365 Account as the parent record and create individual Contacts linked to that Account.

How it maps

This requires an Account first (foreign key resolution order: Account → Contact → Opportunity). Housecall Pro's billing address and service address map to Account address fields; individual contact roles use Contact fields.

transformed

Job → Opportunity + Activities

Jobs are the central Housecall Pro work record.

How it maps

In D365 Sales, jobs map to an Opportunity with associated Tasks for each work activity. Job type, status, priority, and assigned employee map to custom Opportunity fields since D365 Sales has no native job-status concept. Line items (parts and labor) from the job map to Opportunity Product Lines. The property profile linked to the job becomes custom fields on the Opportunity or a custom Equipment entity.

direct

Estimate → Quote

Housecall Pro estimates map directly to D365 Sales Quotes.

How it maps

Estimate line items map to Quote Detail records referencing the product catalog. Estimate status (draft, sent, accepted, rejected) maps to D365 Quote status values. Customer acceptance date maps to the Quote close date. Accepted estimates that converted to jobs link back via a custom Opportunity-Quote reference field.

direct

Invoice → Invoice

Housecall Pro invoices migrate to D365 Sales invoice records.

How it maps

The customer lookup maps to the Contact or Account. Invoice line items (from price book products) map to Invoice Details. Paid status, payment date, and outstanding balance carry over as custom fields since D365 invoice status tracks differently. We preserve the original HCP invoice number for audit traceability.

custom_field_required

Property Profile (Equipment) → Custom Equipment Entity / Contact Fields

Housecall Pro property profiles track equipment at customer addresses (A/C make/model/serial number, install date).

How it maps

D365 Sales has no native equipment entity. We create a custom Equipment entity with fields for item type, make, model, serial number, and install date, linked to the Contact via a 1:N relationship. If the customer has few equipment records, we alternatively store these as custom fields on the Contact itself.

What moves12 objects
Housecall ProDynamics 365
  • CustomerContact1:1
  • CustomerAccounttransformed
  • JobOpportunitytransformed
  • EstimateQuote1:1
  • InvoiceInvoice1:1
  • Property ProfileCustom Equipment Entitytransformed

+ 6 more in the mapping below

How Housecall Pro and Dynamics 365 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.

DimensionHousecall ProDynamics 365
Customer data modelFlat customers with company name; no Account-Contact split; multiple addresses per customer supportedSeparate Account (business) and Contact (individual) entities; one primary address per Contact; multiple Contacts per Account
Job as primary objectJobs are the central work record; job type, status, assigned tech, line items, and property profile all attached to one recordNo native job entity; service records map to Opportunities (pipeline), Tasks/Activities (history), or a custom FieldService entity — each with different reporting implications
Scheduling and dispatchBuilt-in job scheduling and dispatch board; on-the-way notifications; GPS tracking included in platformScheduling requires Dynamics 365 Field Service (separate module/license); D365 Sales core has no native dispatch board
Custom field supportNo custom fields on any object; no custom invoice display, no custom customer properties; feature request backlog onlyUnlimited custom fields on all standard and custom entities; custom fields created via the UI or solution layer
Price book vs. product catalogPrice Book holds service names, descriptions, pricing, categories, and units; linked to jobs as line itemsProduct catalog with Products, Price Lists, and Price List Items; more complex pricing structures (volume discounts, tiered pricing) available
Automation modelBasic workflow rules for notifications and status changes; limited branching logic; no Power Automate equivalentPower Automate + classic workflow rules; full Azure-backed automation with 400+ connectors; significantly broader scope
ReportingBuilt-in dashboard; limited customization; no direct Power BI connectorNative Power BI integration; embedded analytics in Sales Insights; customizable dashboards with AI-driven forecasting
Pricing model$59–$79+/month flat plans; API access locked to MAX plan; add-on costs for Sales Proposal, Pipeline, Voice$65–$150/user/month by tier (Professional/Enterprise/Premium); API access standard; Copilot AI in higher tiers

Housecall Pro to Dynamics 365 field mapping

The 30 most-used fields of 48 mapped for this pair. Custom fields are added from your own schema during scoping. Download the full mapping (CSV) ↓ or open it in the field mapping template.

Field mapping5 shown
Housecall ProDynamics 365
  1. first_nameCustomer FirstNameContact
  2. last_nameCustomer LastNameContact
  3. emailCustomer EmailContact
  4. phoneCustomer Telephone1Contact
  5. mobile_numberCustomer MobilePhoneContact
Housecall Pro fieldDynamics 365 fieldMappingNote
Customer.first_nameContact.FirstNamedirect
Customer.last_nameContact.LastNamedirect
Customer.emailContact.Emaildirect
Customer.phoneContact.Telephone1direct
Customer.mobile_numberContact.MobilePhonedirect
Customer.home_numberContact.Telephone2direct
Customer.work_numberContact.Telephone3direct
Customer.companyAccount.NametransformedWhen company name is present, we create an Account record first and link the Contact to it via ParentCustomerId.
Customer.addressesContact.Address1_Line1, Address1_City, Address1_State, Address1_PostalCode, Address1_CountrytransformedHCP supports billing and service addresses per customer. We map the primary address to Contact address fields; secondary addresses become a custom multi-line field or Account addresses.
Customer.lead_sourceContact.LeadSourcedirect
Customer.notesContact.Descriptiondirect
Customer.tagsContact.HCP_Tags__ccustom_field_requiredD365 has no native tag field. We create a custom text field and concatenate HCP tags as comma-separated values.
Customer.notifications_enabledContact.DoNotEMailvalue_mappingHCP notifications_enabled=true maps to DoNotEMail=false; notifications_enabled=false maps to DoNotEMail=true (inverse logic).
Customer.created_atContact.Original_Create_Date__ccustom_field_requiredD365 CreatedDate reflects migration insertion time. Original HCP create date preserved in a custom datetime field for reporting continuity.
Customer.idContact.Source_System_ID__ccustom_field_requiredHCP customer ID stored for delta-run de-duplication and cross-reference during reconciliation.
Job.nameOpportunity.Namedirect
Job.statusOpportunity.HCP_Job_Status__ccustom_field_requiredD365 Sales has no native job-status concept. We create a custom pick-list field capturing HCP status values (Scheduled, In Progress, Completed, Cancelled).
Job.job_typeOpportunity.HCP_Job_Type__ccustom_field_requiredHCP job types (repair, maintenance, installation) migrate as a custom pick-list on Opportunity.
Job.scheduled_startOpportunity.EstimatedCloseDatetransformedHCP job start date maps to the Opportunity close date field. For open jobs, EstimatedCloseDate is set; for completed jobs, ActualCloseDate__c is used.
Job.total_amountOpportunity.Amountdirect
Job.assigned_employee_idOpportunity.OwnerIdtransformedHCP employee email matched against D365 User email to resolve OwnerId. Unmatched employees flagged before migration.
Job.property_profile_idCustom Equipment.HCP_Property_Profile_ID__ccustom_field_requiredLinks the Opportunity to the corresponding custom Equipment record created from the property profile.
Job.customer_idOpportunity.CustomerIddirect
Job.notesOpportunity.Descriptiondirect
Job.line_itemsOpportunity.OpportunityLineItemsdirect
Job.idOpportunity.Source_System_ID__ccustom_field_requiredHCP job ID stored for delta-run de-duplication.
Estimate.estimate_numberQuote.Namedirect
Estimate.statusQuote.Statusvalue_mappingHCP estimate statuses (Draft, Sent, Accepted, Rejected) map to D365 Quote status values (Draft, Active, Won, Lost). Rejected estimates may optionally map to Lost.
Estimate.total_amountQuote.TotalAmountdirect
Estimate.line_itemsQuoteDetail.ProductId, Quantity, UnitPricedirectHCP estimate line items map to Quote Product records referencing the migrated Product catalog entries.

What to watch for in a Housecall Pro to Dynamics 365 migration

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

high

Housecall Pro API access requires MAX plan — rate limits may extend migration timeline

Housecall Pro's public API is restricted to MAX plan subscribers.

How we handle it

During a migration, FlitStack AI extracts all records via authenticated API calls. The API has undocumented rate limits per account token; under high-volume exports, 429 Too Many Requests responses can throttle the extraction and extend the migration window. We monitor response headers and implement backoff logic, but you should confirm your Housecall Pro plan tier before migration begins — if you are not on MAX, there is no API path and data extraction defaults to CSV batch files, which may not include all objects.

high

Housecall Pro has no custom fields — any custom tracking built outside HCP must be rebuilt in D365 Sales

Housecall Pro's documentation explicitly states that the platform does not support custom fields on any object — not on customer profiles, not on jobs, not on invoices.

How we handle it

If your business has been tracking compliance codes, franchise identifiers, or service-tier levels by storing data in third-party integrations, spreadsheets, or external systems tied to HCP record IDs, that tracking has no native HCP home. When you migrate to D365 Sales, those custom data points need to be mapped to new custom fields on the appropriate D365 entity (Contact, Opportunity, or a custom entity). FlitStack surfaces any external data associations during the discovery phase and adds those fields to the migration plan as custom field mappings.

high

D365 Sales has no native job entity — job-to-opportunity mapping requires custom field strategy

Dynamics 365 Sales is designed for sales pipeline management, not field service operations.

How we handle it

Housecall Pro jobs — which include assigned technician, job type, status, property profile, line items, and appointment times — cannot map to a single native D365 entity. FlitStack maps jobs to Opportunities with associated Tasks and custom fields for HCP-specific attributes (job type, job status, priority, assigned tech). The consequence: service history appears as a list of Opportunities and Activities rather than a single job record in D365. If you rely on job-level reporting (technician utilization, job-type revenue analysis), your admin should create D365 dashboards on the Opportunity + Activity model after migration — or consider licensing Dynamics 365 Field Service separately for its native Work Order entity.

medium

Property profile equipment data requires a custom entity or note-based migration

Housecall Pro's Property Profile app tracks equipment at customer addresses — item type, make, model, serial number, install date, and notes.

How we handle it

Dynamics 365 Sales has no native equipment entity on the Contact record. FlitStack creates a custom Equipment entity in D365 with the same field schema as the HCP property profile, linked to Contact via a 1:N relationship. However, D365 Sales Professional has a 15-table limit on custom entities; Sales Enterprise removes this cap. If you are licensing Sales Professional, discuss whether the Equipment entity fits within your table budget or whether equipment data should instead be stored as structured Notes on the Contact.

medium

Multi-address customers in Housecall Pro map awkwardly to D365's single-address Contact model

Housecall Pro supports multiple addresses per customer (billing address, service address, additional locations).

How we handle it

Dynamics 365 Sales Contacts have one primary address in standard address fields. When a Housecall Pro customer has separate billing and service addresses, FlitStack maps the primary address to Contact.Address1 fields and the secondary address to Contact.Address2 or custom address fields on the Account. For customers with three or more distinct address types, the additional addresses may need to be stored as custom multi-line text fields or require an Account record with multiple Contact roles — both approaches require post-migration admin configuration to display correctly on record layouts.

How the migration runs

  1. Audit Housecall Pro data inventory and API access tier

    Before mapping begins, FlitStack pulls a full inventory of your Housecall Pro data: customer count, job count, invoice count, price book entry count, property profile count, and attachment volume.

    What this step covers

    We verify your Housecall Pro plan tier — if you are not on MAX, API access is unavailable and we plan around CSV batch exports. We also identify any data stored outside HCP (spreadsheets, QuickBooks, third-party tools) that references HCP record IDs and flag those cross-references for manual reconciliation.

  2. Design D365 Sales schema: Accounts, custom entities, and opportunity field architecture

    FlitStack delivers a D365 Sales schema setup plan before data moves.

    What this step covers

    This includes: which Housecall Pro customers become Accounts vs. Contacts, the custom Equipment entity schema for property profiles, custom Opportunity fields for job type and status, and the product catalog structure for your price book. If you are on D365 Sales Professional, we flag the 15-table custom entity limit. If you are on Enterprise or Premium, we confirm that unlimited custom fields and entities are available for the full mapping scope. Your D365 admin creates the schema in a sandbox before FlitStack validates field-level mapping.

  3. Resolve owner and user mapping by email match

    Housecall Pro employees (technicians, office staff) assigned to jobs must be matched to D365 Users by email address.

    What this step covers

    FlitStack generates an owner resolution report: matched employees get their jobs assigned to the corresponding D365 User as Opportunity OwnerId; unmatched employees are flagged with their HCP employee ID so your admin either creates D365 User accounts first or assigns their records to a fallback owner. No Opportunity lands in D365 without a resolved OwnerId.

  4. Migrate in dependency order: Accounts → Contacts → Opportunities → Quotes → Invoices → Activities

    D365 Sales requires foreign key resolution in order: Accounts before Contacts (via AccountId), Contacts before Opportunities (via CustomerId), and Opportunities before Quotes (via OpportunityId).

    What this step covers

    FlitStack sequences the migration so master data lands first (Accounts/Contacts, Products from the price book), then transactional records (Opportunities from jobs, Quotes from estimates, Invoices). Activities (Tasks, Events, Notes) attach to their parent records after the parent IDs are assigned. This prevents orphaned records and failed lookups.

  5. Run sample migration with field-level diff

    A representative slice of 100–500 records — spanning customers, jobs, estimates, invoices, property profiles, and attachments — migrates first.

    What this step covers

    FlitStack generates a field-level diff showing every source value and its destination equivalent. You verify that job type maps correctly to the custom Opportunity field, that equipment make/model lands on the custom Equipment entity, that price book entries appear in the product catalog, and that owner resolution worked for your tech team. Any mapping errors are corrected before the full run commits.

  6. Cut over with delta pickup and audit log

    The full migration runs against your live D365 Sales environment.

    What this step covers

    A delta-pickup window (typically 24–48 hours after the initial extraction timestamp) captures any Housecall Pro records created or modified during the cutover — so D365 reflects HCP's final state at go-live. FlitStack generates a complete audit log of every record inserted, updated, or skipped. One-click rollback reverts all operations if reconciliation against your HCP export report reveals unexpected discrepancies. After go-live, your admin rebuilds HCP workflows in D365 Power Automate and configures integrations with tools like QuickBooks or field-dispatch platforms.

Housecall Pro Dynamics 365
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · Dynamics 365Rollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

48–72 hours for under 50,000 recordsTypical, smaller accounts
5–7 days for over 500,000 records or heavy custom-object / equipment-history setupsLarge or heavily customised accounts

FlitStack AI pricing for Housecall Pro to Dynamics 365 Sales migrations scales with three factors: total record count (customers, jobs, invoices, price book entries), the number of Housecall Pro custom configurations (even without custom fields, price book complexity and property profile density drive mapping work), and the degree of object-model divergence. Housecall Pro's flat customer structure against D365 Sales's Account-Contact hierarchy requires decision-logic — per-customer Account creation vs. Contact-only mapping — that adds planning scope. Migrations with more than 50,000 records or more than 20 price book categories land in the upper pricing tier because field-level diff validation and delta-run reconciliation take longer. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Housecall Pro to Dynamics 365 →

Why teams move from Housecall Pro to Dynamics 365

  • Housecall Pro caps out at flat customer records with no hierarchical relationship model — when home-service businesses grow to multiple locations or commercial/consumer customer segments, the inability to create Account-Contact hierarchies in Housecall Pro forces data duplication and reporting workarounds that Dynamics 365 Sales handles natively with its Account model, territory management, and AI-driven opportunity insights.
  • The Microsoft ecosystem integration argument: D365 Sales connects natively to Office 365, Teams, Outlook, SharePoint, and Power Platform — businesses already running Microsoft tools see reduced context-switching and can trigger Power Automate flows from D365 records without third-party middleware, which Housecall Pro cannot match without costly API add-ons.
  • Pricing model frustration with Housecall Pro add-ons: reviewers on Reddit and G2 report that the base plan cost balloons quickly — Sales Proposal ($40/mo), Pipeline ($50/mo), HCP Voice ($49/mo) stack on top of the Essentials subscription, and the total can exceed $300/month for features that D365 Sales bundles into its per-user license tiers.
  • Custom field requirements that Housecall Pro cannot satisfy: businesses tracking compliance data, franchise-specific codes, or multi-property service history hit Housecall Pro's 'no custom fields' ceiling. Dynamics 365 Sales allows unlimited custom fields on all entities, and the ability to create a custom FieldService entity for equipment tracking directly addresses the property-profile use case that Housecall Pro handles in a separate app.

Questions, answered

Housecall Pro to Dynamics 365 migration questions

How long does a Housecall Pro to Dynamics 365 Sales migration take?

Most Housecall Pro to D365 Sales migrations complete in 48–72 hours for under 50,000 records. Larger datasets with 500,000+ records or extensive property profile histories extend to 5–7 days. The longest planning step is the job-to-opportunity mapping design — deciding which custom Opportunity fields to create for job type, status, and priority, and whether to build a custom Equipment entity for property profiles. API access tier and CSV vs. API extraction method also affect the extraction timeline.

Will my Housecall Pro workflows and automations migrate to Dynamics 365 Sales?

No. Housecall Pro workflow rules, job-dispatch automations, customer notification triggers, and status-change logic do not have an equivalent in D365 Sales — the automation models are fundamentally different. HCP automations must be rebuilt in D365 Power Automate or D365 workflow rules after data migration. FlitStack can export your HCP workflow definitions as a structured reference document your admin uses to recreate the logic in D365 Sales.

What happens to Housecall Pro job records in Dynamics 365 Sales?

Housecall Pro jobs migrate to D365 Sales Opportunities with associated Tasks and custom fields. Job type, status, priority, and assigned technician become custom Opportunity fields. Line items (parts and labor) become Opportunity Product Lines referencing the migrated price book. Property profile data (equipment make/model/serial number) moves to a custom Equipment entity linked to the Contact. If you need native work-order functionality, Dynamics 365 Field Service (a separate license) provides the Work Order entity — discuss this with your Microsoft account executive.

Can I migrate Housecall Pro custom fields to Dynamics 365 Sales?

Housecall Pro does not support custom fields on any object — this is a known platform limitation. If you have been tracking data in external systems tied to HCP record IDs, FlitStack maps those external references to new D365 custom fields on the appropriate entity (Contact, Opportunity, or a custom entity). All HCP custom data points get explicit field-level mapping in the migration plan. D365 Sales custom fields are created in your D365 admin console before migration runs.

What happens to Housecall Pro's property profile equipment data in Dynamics 365 Sales?

Housecall Pro property profiles (equipment item type, make, model, serial number, install date) migrate to a custom Equipment entity in D365 Sales linked to the Contact via a 1:N relationship. This preserves the full equipment history at each customer address. If you are on D365 Sales Professional (15-table limit), we discuss whether to use the Equipment entity or store equipment data as structured Notes on the Contact — both are valid depending on your reporting needs.

Does the migration affect my Housecall Pro account during cutover?

No. FlitStack uses scoped read access on Housecall Pro — your team continues working in HCP throughout the migration. A delta-pickup window (24–48 hours after the initial extraction timestamp) captures any customers, jobs, or invoices created or modified during the cutover. D365 Sales reflects HCP's final state at go-live. FlitStack maintains a complete audit log of all operations, and one-click rollback is available if reconciliation against your HCP export report reveals unexpected discrepancies.

Get a quote

Moving from Housecall Pro to Dynamics 365?

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

Get a quote