The Agile Good Life

Tools & systems

The HubSpot Onboarding Process for Small Teams: What to Configure First and What to Skip

Let HubSpot handle the basics. Spend your time on the data structure.

The HubSpot onboarding process for a small team comes down to four moves. Let HubSpot's guided setup handle the basics. Build your data structure before anyone on your team works in the system. Test it with a small sample import. Then invite your team. Most guides skip the second and third steps, and that's where small teams lose weeks.

This post is for the person running a small team who's doing three jobs at once. You might be a co-founder who also runs sales, or an ops director who also handles the tech stack. Your team knows your industry cold. They don't know CRMs, and that's fine. That isn't their job.

So here's what to configure first, what to skip, and how I actually run the build.

Let HubSpot handle the basics

HubSpot's own setup walks you through company details, branding, colors, and the core settings for sales or marketing. Follow the prompts. When you get stuck, ask Breeze, HubSpot's built-in AI. It knows the product and it's right there.

This part matters a lot. Your brand settings drive your marketing content, and your sales settings shape how your reps work every day. It can feel like the kind of thing you need a consultant for. You don't. You know your brand better than anyone you'd hire, and HubSpot built this part to be self-serve. Spend your money on the part that isn't.

What the guides leave out

HubSpot wants you to believe you can upload a list and start working right away. I get why. They want it to feel easy, and the interface really is friendly.

But getting your data in right takes some technical know-how, and the guides don't stress it enough.

Here's a simple example. Every field in HubSpot has a type: text, number, date, dropdown, and so on. When you import a spreadsheet, you map each column to a field. If you bring a date in as a text field, it looks fine on the record. Then you try to filter contacts by a date range and you can't, because HubSpot doesn't treat that text as a date. I've seen people do this more than once.

The bigger gap is that HubSpot's guides assume the simplest possible setup. HubSpot is a deep tool. There are a lot of features and usually more than one way to reach any goal. No matter how friendly the interface is, it pays to plan before you build.

Import first, organize later: what that costs

One of my clients is a marketing firm that manages leads for leading education technology brands. They target educators, so the details that matter are things like the type of school (high school or college, 2 year or 4 year), plus the person's role and job title. Those details decide which brand a lead belongs to.

Before they brought anyone in, they imported all their contacts. Every one of those structured details came in as a free text field. One record said "2 year." Another said "2YR." Another spelled it out. You can't segment on that cleanly, and you can't build campaigns on it.

Fixing it meant going backward. We exported everything from HubSpot, cleaned it outside the system, and mapped those values to dropdowns. A lot of those school details had to move from the contact record up to the company record, because that's where they actually belonged. Then we re-imported and deleted the temporary text fields that would only have confused the team later. Only after all that could they start building campaigns.

It made adoption take a lot longer. Their goals were never going to work with the original setup.

There was a second lesson. They'd bought Starter expecting it to handle their automation. Starter has some simple automation, but the full workflows tool requires Professional or Enterprise. That's the one you'd use to schedule and run automation across your whole database. That turned into a different conversation: how to make automation work for this team on a real budget.

Plan a build period before your team logs in

If you're migrating real data into HubSpot, your team should not be working in it on day one.

There has to be a build period first. How long depends on how clean and structured your data already is. Tidy spreadsheets with consistent values? Short. Ten years of exports from three different tools? Longer.

When you're buying HubSpot, build that time into the plan. Don't schedule the team kickoff for the day the contract starts.

The build, step by step

Here's how I run the build with a small team. One thing first: I guide, the client decides.

I'm an outside resource. I know HubSpot. I don't know your business the way you do, and I don't know what you value. So I don't decide what lives on the company record and what lives on the contact record. I help you make that call.

The line is often grayer than you'd like, and sometimes a little redundancy helps. Say you want the number of employees on the company record, but you also want it on the contact so segmenting is easier later. You could keep the two in sync with a workflow or a property sync. Or you could ignore the company value and only use the contact one. There's no universal right answer. There's the answer that fits how your team works.

1. Sort out access

If we're working together, I need a paid seat and super admin access in your portal. I'm not a HubSpot affiliate, so I don't get in for free. It sounds obvious, but it's always step one.

2. Look at the data, and protect the originals

If your data is already in HubSpot, we start there. If your portal is a clean slate, we keep it clean and work in spreadsheets outside of HubSpot.

I set up a shared drive where you drop your files. Everything gets backed up. I never overwrite an original. I duplicate and build from the copy, and I label every file clearly so we never have a version problem.

3. Pass one: my first read

I go through your spreadsheet column by column and say where I think each one belongs: company, contact, deal, or another object you might need.

That usually comes with questions. Does this need to be a number field? If you sell in more than one currency, do you need multiple currencies set up? That one changes how your pipeline gets built.

4. Pass two: the database scoping call

We get on a call, look at the data together, and work through any questions you didn't answer on your own.

The goal is to decide, for your core objects (usually companies, contacts, and deals), which fields matter most. The basics come built in: name, email, phone. But maybe you want a WhatsApp number and a mobile number as separate fields. Maybe you need two addresses. That's where custom fields come in, and you want a plan for managing them.

Out of that call, we know the key fields, where they overlap, and what belongs where. I clean the file, get it ready to import, and propose how to create the custom fields and organize them into property groups so they stay tidy.

5. Pass three: import a sample

We import about 100 records per object. 100 contacts, 100 companies, 100 deals if you're bringing in history.

This step does two things. It checks that the data comes in as the right types. And it gives us real records to set up how HubSpot looks for your team: which fields show in the left sidebar, which associations are visible, and what goes in the middle of the record.

We start with one default view for everyone. Once that's working, we talk about reporting. What numbers matter to you? What are your KPIs? In my experience, small teams have this defined the least. Having seen your data, I usually have some suggestions, and I can build a basic dashboard from the sample.

We'll often do this in separate sessions: one for contacts, one for companies, one for deals. If you need service tickets or custom objects, those get their own sample too.

6. Push the rest

Once the sample checks out, we bring in everything else.

Don't skip the sample, especially with a lot of history. Some teams have 20,000 historical records, complete with notes, and they want all of it in there. That can't happen in one shot. The sample is how we find out what's possible, what isn't, and what your specific plan can do to bring in that history.

If you're doing the import yourself

You can absolutely do this on your own. Before you touch the importer, read two of HubSpot's help docs all the way through:

The good news: nothing here is irreversible. You can always export, fix, and re-import. It just takes a technical mindset to get it right the first time, and getting it right the first time is a lot cheaper than the cleanup.

What to skip for now

Onboarding is about the foundation. Leave these for later:

  • Team-specific views and detailed permissions. If you have several teams and want different visibility for each, HubSpot can get very granular. Start with one default view and adjust once people are actually using it.
  • The details of your processes. How your sales process runs, how ticketing works, how you plan marketing campaigns. Those builds come after the foundation is solid and looks consistent for everyone.

Invite your team last

Once the foundation is built and the data is in, bring your team in. Now they log into a system that already makes sense, with their real data and fields they recognize.

When you get to setting up your reps, use my HubSpot onboarding checklist for sales reps. It picks up where this post stops.

Your three options for help

Here's what a lot of small teams don't hear before they buy: getting onto HubSpot the right way can cost more than the subscription suggests.

You have three real options:

  1. HubSpot's own onboarding. On Professional and Enterprise plans it's a required one-time fee. For Sales Hub it's $1,500 at Professional and $3,500 at Enterprise. Marketing Hub Professional runs $3,000.
  2. A HubSpot partner agency. Good partners exist, but agencies are built and priced for bigger engagements.
  3. A solo operator. Someone who does this every day for small teams, across a lot of different setups.

I'm the third option. If you want help with the build, let's talk.

Before you buy anything: list your jobs to be done

If you do one thing after reading this, make this list.

Write down the jobs you need your CRM to do. Start from what your people actually do. If you want your SDR making 100 calls a day, then your CRM needs to log calls. Maybe you want those calls transcribed too.

Then put that list into ChatGPT, Claude, or whatever AI tool you use, and have it research HubSpot's current plans and pricing against your list. A paid account does this better, but any of them will get you started.

This is where you find out the real cost. Take call transcription. HubSpot only transcribes calls for users on a Sales Hub or Service Hub Professional or Enterprise seat. On top of that, you need a calling setup, either HubSpot's own calling or a third-party provider you pay for separately. If you went in thinking HubSpot was the budget option, that's the kind of thing that makes the cost balloon. A clear list catches it before you sign.

If you want a second opinion on which plan and how many seats make sense, I'll give you 30 minutes for free. It's a no-pitch call. I won't sell you my services. We'll look at your team size, your budget, and what you need HubSpot to do, and I'll give you an outside view of what HubSpot offers that you may not get from them directly. HubSpot is built to be self-serve, and unless you're a bigger account, it can be hard to get a straight answer from a person. Book the call here.

Whatever you set up first, it's the starting line, not the finish line. You'll make compromises. Your team will grow. Some decisions will change as your strategy gets clearer. That's normal. Agile doesn't mean throwing out the plan. It means building one you can adjust.