---
title: "ServiceTitan to HubSpot Migration: Field Mapping & Rollback"
description: "Migrate ServiceTitan 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/servicetitan/to/hubspot"
---

# ServiceTitan to HubSpot migration

Moving from ServiceTitan to HubSpot consolidates your field-service customer records into HubSpot's CRM model — mapping every Customer, Location, Job, Equipment, and Membership to the right HubSpot object so your service history, technician assignments, and membership tiers survive the transition intact.

Short answer

FlitStack AI migrates contacts, companies, deals, custom objects and users from ServiceTitan 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: 72–96 hours for under 50,000 ServiceTitan records with standard object mapping..

![](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/servicetitan/to/hubspot#field-mapping)

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

Source ServiceTitan ![](https://flitstack.ai/platforms-trim/servicetitan.webp)

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

Contact Company Deal Custom Object User

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

## What moves from ServiceTitan to HubSpot?

ServiceTitan organizes field-service data around Customers, Locations, Jobs, Equipment, Invoices, and Memberships — a model optimized for dispatch, technician routing, and job costing.

Read the full summary

HubSpot organizes data around Contacts, Companies, Deals, and Custom Objects with lifecycle stages and deal pipelines for sales-driven visibility. FlitStack AI maps each ServiceTitan entity to its nearest HubSpot analogue: Customers map to Contacts with a primary Location becoming a Company record, Jobs map to Deals with stage reflecting job status, Equipment maps to a HubSpot Custom Object for asset lifecycle tracking, and Memberships map to either a custom Membership object or Deal-level recurring properties depending on renewal mechanics. ServiceTitan's per-technician pricing (currently $245–$500+ per tech per month) makes HubSpot's per-seat or per-hub model attractive for teams scaling headcount. HubSpot's native marketing automation, reporting, and Breeze AI tools are not available inside ServiceTitan — the migration opens access to those capabilities but the automation logic (ServiceTitan dispatch rules, automatic invoicing triggers, and workflow actions) does not transfer and must be rebuilt in HubSpot's automation tools.

direct

### Customer → Contact

ServiceTitan Customer maps directly to HubSpot Contact.

How it maps

The primary phone, email, name, and address fields transfer as standard Contact properties. Secondary contact records attached to a Customer become additional HubSpot Contact records linked to the same primary Company in HubSpot.

direct

### Location → Company

ServiceTitan Location (the physical service site with address) maps to HubSpot Company.

How it maps

Multi-location customers generate multiple Company records with a custom Location\_ID\_\_c field and optional parent-company linkage. ServiceTitan location-type tags (residential, commercial) map to a custom Company property in HubSpot.

direct

### Job → Deal

ServiceTitan Job maps to HubSpot Deal.

How it maps

Job status (Created, Dispatched, In Progress, Completed, Invoiced) maps to HubSpot Deal stage. The Job total revenue maps to Deal amount, technician assignment maps to a custom Owner\_ Technician\_\_c property, and job\_type maps to a custom Job\_Type\_\_c property on the Deal.

direct

### Estimate → Deal

ServiceTitan Estimates become HubSpot Deals in 'Proposal' or pre-dispatch stages.

How it maps

Estimate line items with description and price are stored as Deal property text (multi-line) or as a custom line-item object. Converting an Estimate to a Job in ServiceTitan maps to advancing the HubSpot Deal to a won/active stage.

transformed

### Invoice → Deal

ServiceTitan Invoice records preserve financial history but HubSpot has no native invoice object.

How it maps

Invoice total, status (Paid, Outstanding, Overdue), and invoice date are stored as custom properties on the associated Deal: Invoice\_Total\_\_c, Invoice\_Status\_\_c, Invoice\_Date\_\_c. Full invoice line items require a custom Invoice\_Line\_Item\_\_c object.

custom\_field\_required

### Equipment → Custom Object (Equipment)

ServiceTitan Equipment (serialized HVAC units, water heaters, appliances) has no native HubSpot equivalent.

How it maps

We create an Equipment custom object with properties for Asset\_Tag\_\_c, Make\_\_c, Model\_\_c, Serial\_Number\_\_c, Install\_Date\_\_c, Warranty\_Expiration\_\_c, and a lookup to the HubSpot Company representing the Location where the equipment is installed.

******What moves 12 objects

ServiceTitan HubSpot

- Customer Contact 1:1
- Location Company 1:1
- Job Deal 1:1
- Estimate Deal 1:1
- Invoice Deal transformed
- Equipment Custom Object transformed

\+ 6 more in the mapping below

## How ServiceTitan 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                   | ServiceTitan                                                                                                                                                  | HubSpot                                                                                                                                                                                     |
| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Core data model             | ServiceTitan uses Customers + Locations + Jobs + Equipment as primary objects with Business Units and Technicians as operational sub-entities.                | HubSpot uses Contacts + Companies + Deals + Custom Objects as primary objects. Associations between contacts and companies support primary and secondary roles.                             |
| Pricing structure           | ServiceTitan charges per technician per month ($245–$500+ depending on tier) with add-on module costs.                                                        | HubSpot charges per seat per hub or per workflow action. Starter CRM begins at $50/month with marketing and operations hubs at higher tiers.                                                |
| Job / deal representation   | ServiceTitan Jobs carry a full lifecycle: created → dispatched → in-progress → completed, with line-item invoices and technician assignments on every record. | HubSpot Deals represent sales pipeline stages (Appointment Scheduled → Quote Sent → Decision Maker Bought In, etc.) and do not natively carry technician assignment or job-cost line items. |
| Location vs. company model  | ServiceTitan Locations are service-site records (addresses) attached to a Customer, supporting multi-location customers with separate job histories per site. | HubSpot Companies represent business entities with a single address; multi-site customers require multiple Company records or a custom junction object for site-level history.              |
| Automation scope            | ServiceTitan automations govern dispatch rules, job-status triggers, automatic invoice generation, and technician notifications.                              | HubSpot workflows govern contact-property changes, deal-stage triggers, email enrollment, and task creation. No dispatch or job-costing logic is available.                                 |
| Equipment / asset tracking  | ServiceTitan Equipment stores serialized assets (HVAC units, water heaters) with make, model, serial number, and install date linked to a Location.           | HubSpot has no native asset object. Equipment data requires a HubSpot Custom Object with serial number, asset type, install date, and location link as custom properties.                   |
| Membership / contract model | ServiceTitan Memberships store tier (Gold, Silver, Bronze), renewal date, covered locations, and benefit definitions.                                         | HubSpot has no native membership equivalent. Migrations typically create a Custom Object for membership tiers or store renewal cadence and tier on the associated Company record.           |

## ServiceTitan to HubSpot field mapping

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

******Field mapping 5 shown

ServiceTitan HubSpot

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

| ServiceTitan field         | HubSpot field                     | Mapping                 | Note                                                                                                                                               |
| -------------------------- | --------------------------------- | ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Customer.first_name`      | `Contact.firstname`               | direct                  |                                                                                                                                                    |
| `Customer.last_name`       | `Contact.lastname`                | direct                  |                                                                                                                                                    |
| `Customer.email`           | `Contact.email`                   | direct                  |                                                                                                                                                    |
| `Customer.phone`           | `Contact.phone`                   | direct                  |                                                                                                                                                    |
| `Customer.mobile_phone`    | `Contact.mobilephone`             | direct                  |                                                                                                                                                    |
| `Customer.home_phone`      | `Contact.homephone`               | direct                  |                                                                                                                                                    |
| `Customer.company_name`    | `Contact.company`                 | direct                  | Maps to HubSpot contact company property; primary Location must be migrated as Company first.                                                      |
| `Customer.customer_type`   | `Contact.customer_type__c`        | custom\_field\_required | Residential / Commercial tag from ServiceTitan becomes a custom pick-list on HubSpot Contact.                                                      |
| `Customer.created_date`    | `Contact.original_create_date__c` | custom\_field\_required | HubSpot CreatedDate is set at migration time; original ServiceTitan create date preserved as custom datetime.                                      |
| `Customer.st_customer_id`  | `Contact.source_system_id__c`     | custom\_field\_required | ServiceTitan internal ID stored on Contact for traceability and delta-run de-duplication.                                                          |
| `Location.location_name`   | `Company.name`                    | direct                  |                                                                                                                                                    |
| `Location.street_address`  | `Company.address`                 | direct                  |                                                                                                                                                    |
| `Location.city`            | `Company.city`                    | direct                  |                                                                                                                                                    |
| `Location.state`           | `Company.state`                   | direct                  |                                                                                                                                                    |
| `Location.zip_code`        | `Company.zip`                     | direct                  |                                                                                                                                                    |
| `Location.location_type`   | `Company.location_type__c`        | custom\_field\_required | Residential vs. Commercial stored as a custom pick-list on the Company record.                                                                     |
| `Location.st_location_id`  | `Company.source_system_id__c`     | custom\_field\_required | ServiceTitan Location ID preserved for association mapping and delta validation.                                                                   |
| `Job.job_number`           | `Deal.dealname`                   | direct                  | ServiceTitan Job Number becomes HubSpot Deal name for identification.                                                                              |
| `Job.job_status`           | `Deal.dealstage`                  | value\_mapping          | Job status (Created → Dispatched → In Progress → Completed → Invoiced) maps to HubSpot Deal stage values. Mapping table applied per status string. |
| `Job.job_type`             | `Deal.job_type__c`                | custom\_field\_required | Repair, Maintenance, Installation — stored as a custom pick-list on the Deal.                                                                      |
| `Job.total_amount`         | `Deal.amount`                     | direct                  |                                                                                                                                                    |
| `Job.scheduled_date`       | `Deal.closedate`                  | direct                  | Scheduled job date maps to HubSpot Close Date for reporting purposes.                                                                              |
| `Job.technician_name`      | `Deal.assigned_technician__c`     | custom\_field\_required | Technician name stored as a custom text field on Deal since HubSpot Users are CRM seats, not field technicians.                                    |
| `Job.business_unit`        | `Deal.business_unit__c`           | custom\_field\_required | ServiceTitan Business Unit stored as a custom text property on Deal for segmentation.                                                              |
| `Job.st_job_id`            | `Deal.source_system_id__c`        | custom\_field\_required | ServiceTitan Job ID preserved for association mapping and invoice linkage.                                                                         |
| `Estimate.estimate_number` | `Deal.dealname`                   | direct                  | Estimate number becomes Deal name; estimate status drives initial Deal stage.                                                                      |
| `Estimate.estimate_amount` | `Deal.amount`                     | direct                  |                                                                                                                                                    |
| `Estimate.estimate_status` | `Deal.dealstage`                  | value\_mapping          | Pending, Approved, Declined, Converted map to HubSpot stage values via value-mapping table.                                                        |
| `Invoice.invoice_number`   | `Deal.invoice_number__c`          | custom\_field\_required | Invoice number stored as custom property on the associated Deal.                                                                                   |
| `Invoice.invoice_total`    | `Deal.invoice_total__c`           | custom\_field\_required | Total amount from ServiceTitan invoice preserved as custom currency field on Deal.                                                                 |

## What to watch for in a ServiceTitan 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

### ServiceTitan Locations become separate Company records, breaking HubSpot's single-primary-account-per-contact assumption

HubSpot Contact records expect a single primary Company via the native company association.

How we handle it

ServiceTitan's multi-location customers have N Location records under one Customer. FlitStack AI maps each ServiceTitan Location to a separate HubSpot Company, then links the Contact to the primary Location as the native Company association and attaches secondary Locations via HubSpot's secondary-company association or a custom junction object. If your ServiceTitan customer has 5 service sites, those 5 sites become 5 Company records in HubSpot — your CRM team needs to understand this split before migration so reports and dashboards are configured correctly.

high

### Job-to-Deal stage mapping requires a value-by-value table, not a simple rename

ServiceTitan job statuses (Created, Dispatched, In Progress, Completed, Invoiced) have no direct HubSpot Deal stage equivalents — HubSpot's default stages (Appointment Scheduled, Qualified to Buy, etc.) are sales-closing stages, not job-operations stages.

How we handle it

FlitStack AI creates a custom job-pipeline in HubSpot with stages that map 1:1 to ServiceTitan job statuses, preserving the original status label and probability. If you also use ServiceTitan Estimates that convert to Jobs, those Estimates need their own pipeline mapping to the same custom pipeline. The custom pipeline must be created in HubSpot before the migration run — we provide the pipeline setup plan as part of the discovery output.

medium

### Equipment and Membership require HubSpot Custom Objects, which require Enterprise-tier licensing

HubSpot Custom Objects are available only on Enterprise-tier subscriptions.

How we handle it

If your ServiceTitan account uses Equipment records for serialized asset tracking and Membership records for preventive-maintenance programs, those objects map cleanly in the migration logic but will land as HubSpot Custom Objects only if your HubSpot portal is on Enterprise. We confirm the destination portal tier before mapping Equipment and Membership — if the portal is Starter or Professional, Equipment and Membership data still migrates but into custom properties on Company or Deal records rather than dedicated objects, and your team should plan a HubSpot upgrade if the full schema is required.

medium

### ServiceTitan's native HubSpot integration is discontinued, creating a data-sync gap during migration planning

ServiceTitan's community forum confirms the native HubSpot integration is no longer supported.

How we handle it

Teams that relied on that integration for real-time job-outcome syncing will have no active sync path during the migration window. FlitStack AI uses scoped read access on the ServiceTitan API (rate-limited at 60 calls/second for regular APIs) to extract data without affecting dispatch operations. Any bi-directional sync use case must be rebuilt post-migration using HubSpot's native integrations or a middleware platform — we document the required sync triggers as part of the post-migration handoff.

low

### Technician assignments on Jobs cannot populate HubSpot User lookups without CRM seat provisioning

ServiceTitan technicians are operational staff who may not need HubSpot CRM seats.

How we handle it

HubSpot's OwnerId field on a Deal expects a User record with an active CRM license. FlitStack AI resolves technician assignments by matching the technician's email against HubSpot Users — if the technician has a HubSpot seat, OwnerId populates natively. If not, the technician name and ServiceTitan ID are stored in a custom Assigned\_Technician\_\_c field on the Deal. This means field-technician reporting in HubSpot requires either provisioning CRM seats for technicians or accepting the custom-field workaround for historical reporting.

## How the migration runs

1. ### Enumerate ServiceTitan objects and plan HubSpot schema

   We connect to your ServiceTitan account via scoped API read access and enumerate every active object: Customers, Locations, Jobs, Estimates, Invoices, Equipment, Memberships, and all custom fields.

   What this step covers

   We produce a schema plan specifying which HubSpot custom objects and custom properties need to be created, what pick-list values need to be defined, and whether your HubSpot portal is on Enterprise for custom object support. This plan is delivered before any data moves.

2. ### Resolve owner and technician identities by email match

   ServiceTitan technicians and office staff are matched against HubSpot Users by email address.

   What this step covers

   Customers with email addresses are matched to existing HubSpot Contacts if any records already exist to prevent duplicates. Unresolved owners and technicians are flagged with a pre-migration report so your team can either provision HubSpot seats for technicians or confirm the custom-field fallback approach before the migration run commits.

3. ### Sequence the migration: Locations → Customers → Jobs → Equipment → Memberships

   HubSpot requires Companies to exist before Contacts (for the native company association) and Contacts before Deals (for deal-contact linking).

   What this step covers

   We sequence the migration in dependency order: Locations→Companies, then Customers→Contacts, then Jobs→Deals with Location and Customer associations resolved by the stored source\_system\_id\_\_c cross-reference. Equipment and Membership custom objects are created after their parent Companies and Contacts are confirmed present in HubSpot.

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

   A representative slice — typically 200–500 records spanning Customers, Locations, Jobs, Equipment, and Memberships — migrates first.

   What this step covers

   We generate a field-level diff showing every source field, its mapped destination value, and any transformation applied (value mappings, type casts, custom property creation). You verify the Job→Deal stage mapping, Equipment associations, and Membership tier values before the full run proceeds. Schema mismatches found at this stage are corrected before scaling.

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

   The full migration extracts and transforms all ServiceTitan records.

   What this step covers

   A delta-pickup window (typically 24–48 hours after full extraction) captures any records created or modified in ServiceTitan during the cutover. FlitStack AI generates an audit log of every record inserted or updated in HubSpot. If reconciliation reveals data integrity issues, one-click rollback reverts the HubSpot portal to its pre-migration state so the run can be corrected and re-executed.

![](https://flitstack.ai/platforms/servicetitan.png) ServiceTitan ![](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

**72–96 hours for under 50,000 ServiceTitan records with standard object mapping.** Typical, smaller accounts

**7–14 days for over 200,000 records or setups with custom objects, multi-location hierarchies, and membership program data.** Large or heavily customised accounts

A quote scales with record volume, custom property count, and the number of distinct ServiceTitan objects being mapped. Standard migration of Customers, Locations, Jobs, and Activities for a single-location contractor typically lands at the lower end. Multi-location setups with Equipment custom objects, Membership custom objects, and invoice-level financial history push toward the upper range because each custom object type requires its own schema mapping and association validation. Large job histories (over 100,000 Jobs) also increase scope because Deal stage mapping and technician assignment fields require per-record transformation. Every quote is scoped with you; there is no self-serve pricing.

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

## Why teams move from ServiceTitan to HubSpot

- ServiceTitan's per-technician pricing compounds quickly as field crews grow — contractors report costs of $10,000+ per month for mid-sized operations and feel locked into annual contracts with opaque exit terms. HubSpot's per-seat pricing with bundled CRM tiers offers better predictability at scale.
- Contractors running ServiceTitan alongside HubSpot for marketing report constant friction exporting ServiceTitan job outcomes and attributing revenue back to HubSpot leads — the native integration is no longer available, forcing teams into middleware workarounds that break under load and require ongoing maintenance.
- ServiceTitan's reporting tools are scoped to operational metrics (dispatch efficiency, job completion rate) but lack the marketing attribution, deal velocity, and cohort analysis that growing contractors need for investor reporting and growth planning. This gap forces teams to maintain separate analytics tools outside ServiceTitan.
- Contractors exploring exit or acquisition want HubSpot's CRM data standardized for due-diligence processes — ServiceTitan's field-service data model is not compatible with standard M\&A data rooms or private-equity reporting templates, which adds time and cost to deal closings and increases due diligence complexity.
- HubSpot's Breeze AI, available across CRM, marketing, and service hubs, offers capabilities (AI-powered lead scoring, conversation intelligence, content generation) that ServiceTitan has not matched, and migrating to HubSpot opens those tools immediately without additional licensing or configuration for most teams.

Questions, answered

## ServiceTitan to HubSpot migration questions

How long does a ServiceTitan to HubSpot migration take?

Most ServiceTitan-to-HubSpot migrations complete in 72–96 hours for under 50,000 records. Multi-location contractors with Equipment and Membership data, or setups exceeding 200,000 Job records, extend to 7–14 days because each distinct ServiceTitan object type requires its own schema creation, dependency sequencing, and field-level validation before the full run. The longest single step is typically building the custom pipeline for job-status-to-Deal-stage mapping and confirming that HubSpot Enterprise is active for custom objects.

Will my ServiceTitan automations migrate to HubSpot workflows?

No. FlitStack AI migrates data and schema only — ServiceTitan dispatch rules, automatic invoice-generation triggers, job-status notification workflows, and technician routing automations do not transfer. They must be rebuilt in HubSpot's automation tools (workflows, sequences, or the Operations Hub). We export your ServiceTitan automation definitions as a structured reference document so your HubSpot admin has a rebuild checklist rather than starting from scratch. Any bi-directional sync logic between ServiceTitan and a marketing platform will also need a new integration design.

What happens to my ServiceTitan Equipment records in HubSpot?

ServiceTitan Equipment (serialized assets like HVAC units and water heaters) maps to a HubSpot Custom Object called Equipment, with properties for Asset\_Tag\_\_c, Serial\_Number\_\_c, Make\_\_c, Model\_\_c, Install\_Date\_\_c, and Warranty\_Expiration\_\_c. Each Equipment record is linked to the HubSpot Company representing the service location where it is installed. Custom Objects require HubSpot Enterprise licensing — if your destination portal is on a lower tier, Equipment data migrates to custom properties on the associated Company record instead.

Can I migrate ServiceTitan Membership programs to HubSpot?

Yes. ServiceTitan Memberships (Gold, Silver, Bronze preventive-maintenance tiers) map to a HubSpot Membership custom object with fields for Tier\_\_c, Renewal\_Date\_\_c, Monthly\_Price\_\_c, Covered\_Locations\_\_c, and Active\_\_c. The Membership links to the primary Contact and to the Company records representing the covered service sites. HubSpot's Operations Hub is recommended for building renewal-date workflows that trigger outreach when a membership is approaching expiration. This approach preserves tier benefits, pricing, and coverage scope across the migration.

How does ServiceTitan's multi-location customer model map to HubSpot?

ServiceTitan allows one Customer record with multiple Location records — a common pattern for commercial customers with separate service sites. FlitStack AI maps each Location to a separate HubSpot Company record with a shared source\_system\_id\_\_c reference back to the originating Customer. The primary Location becomes the Contact's native Company association; additional Locations are accessible as secondary Company associations or via a custom junction object. This means HubSpot dashboards will show multiple Company records for one customer — your CRM team should segment reports by Location rather than by Customer to maintain the same view as ServiceTitan.

Does the migration affect my ServiceTitan account during the cutover?

No. FlitStack AI uses scoped read-only API access on ServiceTitan — your dispatchers and technicians continue working in ServiceTitan without any performance impact. The integration reads records and associations without writing back to ServiceTitan. A delta-pickup window of 24–48 hours after the main extraction captures any Jobs created or modified during the migration window so HubSpot reflects ServiceTitan's final state at go-live.

What happens to my ServiceTitan Invoice and payment history?

HubSpot has no native invoice object, so ServiceTitan Invoice records map to custom properties on the associated Deal: Invoice\_Number\_\_c, Invoice\_Total\_\_c, Invoice\_Status\_\_c (Paid, Outstanding, Overdue), and Invoice\_Date\_\_c. For detailed payment-level history, we recommend a custom Payment\_Record\_\_c object if your HubSpot tier supports custom objects. Job cost line items (parts and labor breakdown) can be stored as a custom text property or custom line-item object — FlitStack AI preserves the full invoice total and status, which is sufficient for most CRM reporting use cases.

How do I handle ServiceTitan Business Units in HubSpot?

ServiceTitan Business Units segment operations by trade or subsidiary (e.g., HVAC Division, Electrical Division). HubSpot has no native business-unit object. FlitStack AI stores the Business Unit name as a custom Contact and Deal property (Business\_Unit\_\_c). For reporting segmentation, we recommend using HubSpot's Teams feature — create one team per Business Unit and assign the relevant Deals and Contacts to each team. This enables per-division pipeline reporting without modifying the record schema.

## 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) [**Dubsado to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/dubsado/to/hubspot) [**Snovio to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/snovio/to/hubspot) [**Customer.io to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/customer-io/to/hubspot) [**ForceManager CRM to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/forcemanager-crm/to/hubspot) [**Gold-Vision to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/gold-vision/to/hubspot) [**improveit 360 to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/improveit-360/to/hubspot) [**ServiceTitan to Zoho CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/servicetitan/to/zoho-crm) [**ServiceTitan to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/servicetitan/to/salesforce-sales-cloud)

## 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 ServiceTitan 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)
