HubSpot Data Hub: what it does and when it’s worth it

What is HubSpot Data Hub (formerly Operations Hub)?

Data Hub is the HubSpot product for the data behind your CRM. It connects HubSpot with other systems, keeps records clean and reshapes data for reports and automation. HubSpot renamed Operations Hub to Data Hub at INBOUND in September 2025 and added Data Studio and the data quality overview. The Operations Hub tools are still there under the new name.

Do you need HubSpot Data Hub? What the free tools already do

Many teams pay for Data Hub to get something they already have. Check this list before you buy.

• Data sync with default mappings. HubSpot’s own sync apps run on every plan, including the free tools. Only your own field mappings need Data Hub.
• The data quality overview. Duplicates, formatting issues and property insights come with every Starter, Professional and Enterprise hub.
• Merging duplicates one pair at a time. Every Professional hub includes it. Our duplicates guide shows the order of work.
• Workflows and calculated properties. Marketing, Sales and Service Hub Professional include both. Data Hub adds code, webhooks and scheduled triggers.
• One-off clean-ups. Cleaning a file in a spreadsheet before you import it is faster than any rule in HubSpot.

Audit the portal before you buy. Most data problems start where data comes in, and a new tool rarely fixes that. The portal audit guide covers that check.

Data Hub Starter, Professional or Enterprise: which job needs which edition

The edition follows the job. Starter is enough for your own sync mappings, Professional for code, rules and Data Studio, Enterprise only for warehouse sync and custom objects.

Is Data Hub Professional worth it?

Data Hub Professional is worth it when one job you can name needs it, runs every week, and would otherwise cost you a middleware plan, a developer or regular manual work.

Data Hub Professional is rarely worth it for a single formatting fix, a one-off import or a sync that the default mappings already cover. Clean the import in a spreadsheet. Map a few extra fields with Starter.

Compare the price with the real alternative: a middleware plan plus the time to maintain it, or a developer’s hours. Count who maintains the code, too. A custom code action needs someone in your team or ours who can read JavaScript or Python.

HubSpot data quality tools: what they fix, and the traps in German data

The data quality overview shows duplicates, formatting issues and empty or unused properties in one place. You find it under Data Management > Data Quality.

1. Step 01

   Open the data quality overview

   Go to Data Management > Data Quality, tab Overview. The summary counts duplicate and formatting issues for the date range you pick. Below it, HubSpot recommends actions, such as reviewing unused workflows or reconnecting an app sync.

   

2. Step 02

   Review formatting issues by type

   Open the tab Formatting issues. Contacts are checked for name, email and location. Each row shows the current value and HubSpot’s proposed fix. Accept or reject one at a time, or in bulk from Data Hub Starter.

   

3. Step 03

   Check location suggestions before you accept them

   HubSpot proposes country codes and English city names, also in a German-language account. “Deutschland” and “germany” become “DE”, “Wien” becomes “Vienna”, “München” becomes “Munich”. Lists, workflows and letters that use the German names then miss records or look wrong. Decide on one standard first, for example the ISO code in Country and the local name in City, and accept only what fits it.

   

4. Step 04

   Automate the safe fixes

   With Data Hub Professional, Actions > Automation turns on rules for capitalisation, combined fields and spacing. HubSpot fixes current records at once and new records as they come in. There is no automation rule for location, so country and city fixes stay manual.

   

Custom code in HubSpot workflows: a phone number clean-up, step by step

A custom code action runs your own JavaScript or Python inside a workflow. Custom code is the main reason teams buy Data Hub Professional. The action does what standard actions can’t, without a separate middleware tool.

Example: phone numbers in one format. Contacts arrive as “0171 1234567”, “+49 (0)89 1234 567” or “0043 664 1234567”. Each format makes the same number look different to reports, duplicate checks and calling tools. This workflow turns them all into the international format, such as +491711234567.

1. Step 01

   Trigger on the phone number

   Create a contact workflow with the trigger Phone number is known. Leave it off until the test passes.

   

2. Step 02

   Add the custom code action

   Add the action Custom code with the language Node.js. Under Property to include in code, add phone and country. The code turns a leading 00 into +, replaces a leading 0 with the country code from the contact’s country, and returns the result. The code needs no secret, because it doesn’t call HubSpot’s API.

   

3. Step 03

   Define the outputs and test

   Add the outputs phone_clean (string) and changed (boolean). Under Test action, pick a contact and run the test. The test runs on the real record, so use a test contact whenever your code writes data.

   

4. Step 04

   Write the result back

   Add the action Edit record and set Phone number to the output phone_clean from the custom code. Then turn the workflow on, and enrol existing contacts if you want to clean the backlog too.

HubSpot Data Studio: datasets with HubSpot and outside data

Data Studio builds datasets: tables that join HubSpot objects with each other and with outside data, with formula columns on top. You find it under Data Management > Data Studio. Data Studio needs Data Hub Professional or Enterprise and is still marked beta (October 2026).

Example: won revenue by company and country. The dataset joins deals with their companies and adds a formula column for the won amount. Use the property “Is closed won” in such formulas, not a stage. Each pipeline has its own won stage, and a formula on one of them misses the others.

Outside data comes in as files, from Google Sheets, from sync apps or from warehouses such as Snowflake. When you connect a sync app, HubSpot now asks whether its data goes straight to the CRM or into Data Studio. Choose Data Studio when the data needs combining or cleaning before it belongs on a record.

Data Studio isn’t a BI tool or a content editor, and it can’t search or change website pages. Its limits are 200 datasets, five joined sources per dataset and 10 GB of outside data.

Data sync with Data Hub Starter: your own field mappings

Data Hub Starter adds your own field mappings to HubSpot’s sync apps. Without it, an app such as Business Central or Pipedrive syncs only HubSpot’s default fields.

• Direction per field. Data the ERP owns flows one way into HubSpot.
• Saving restarts the sync. Each save starts the initial sync again. With many records that takes hours, with millions it can take days.
• Every app differs. Default mappings and matching rules depend on the app. Our ERP guide and the Business Central guide cover the traps.

For many ERP and accounting connections, Starter is all the Data Hub you need. Logic that decides something, such as which record wins or when to create a deal, needs Professional or middleware.

How much does HubSpot Data Hub cost? Prices, seats and credits

Data Hub Starter costs 20 € per seat a month. Professional starts at 790 € and Enterprise at 1,960 € a month, each with one Core seat (HubSpot list prices before VAT, as of October 2026).

Seats are priced at the highest edition you hold. Add Data Hub Professional to Sales Hub Starter and every Core seat is billed as a Professional seat. Price the whole account, not only the hub.

New customers in Europe buy differently since 1 October 2026. They pick one edition for the whole account, with GTM and Ops seats, and there is no separate Data Hub. Warehouse sync is an add-on at 1,000 € a month. Our seats and credits guide explains both models and who needs which seat.

What breaks when you downgrade Data Hub

Data Hub features run only while you pay for them. Plan the exit before you build.

Keep one list of every custom code action and every custom mapping: what it does, which properties it writes and who owns it. The same list serves as your exit plan and your handover.

Data Hub in Germany, Austria and Switzerland

• English defaults. The location suggestions follow English conventions, also in a German-language account. Agree your standard before anyone clicks Accept all.
• Umlauts and ß. HubSpot’s case functions in Format data are documented for the Latin alphabet. Test names with umlauts and ß on a few records before you run them on all.
• Phone numbers. Store them in the international format with +49, +43 or +41. Numbers with a leading 0 only work inside one country and look different in every report.
• Personal data on the move. Syncs and Data Studio copy personal data between systems. Add each connected system to your record of processing activities. Whether a transfer is covered is for your data protection officer to decide.

How we decide on Data Hub

We decide in five steps, and the job comes first.

1. Step 01

   Name the job

   One or two jobs Data Hub should do, how often they run, and what they cost today in hours or tools.
2. Step 02

   Check what you have

   Free data sync, the data quality overview and the workflows in your hubs. Most teams use far less of them than they pay for.
3. Step 03

   Pick the smallest edition

   Take the lowest edition in the edition table that covers every job on your list.
4. Step 04

   Build one job first

   One workflow or one dataset, tested on test records, with a named owner and a written exit plan.
5. Step 05

   Measure, then extend

   After a month, compare hours saved and errors avoided with the price. Then add the next job.

Frequently asked questions