HubSpot Implementation Checklist: 30 Steps Before You Go Live

You just got HubSpot. The portal is empty and blinking at you. Now what?

This is the checklist I run on every HubSpot implementation. Thirty steps, plain English, no assumed knowledge. Work through them in order and your team will have something that actually works when they go live.

Phase 1: Decide How You'll Organize Your Information

Before you do anything else, you need to decide what you're going to track and how. Think of this like setting up a filing system before you start adding files. Get the drawers wrong now and you'll be reorganizing everything in six months.

1. Look at your existing contacts before you import them. If you're bringing contacts in from a spreadsheet or another CRM, open that file first. How messy is it? Duplicate entries, missing company names, and inconsistent formatting are much faster to clean up before they're in HubSpot than after.
2. Figure out which fields you actually need. HubSpot comes with a lot of built-in fields (called properties) for contacts and companies. Before you create any new ones, check if HubSpot already has what you need. Every field you add is something your team has to fill in later.
3. Link your contacts to their companies. In HubSpot, contacts and companies are separate records that get connected. Decide now: should every contact have a company attached? For most B2B teams, yes. This affects how your reports and deal records work.
4. Decide what doesn't belong in HubSpot. HubSpot is for sales and marketing data. It shouldn't hold a copy of everything in every other tool you use. Write a simple list: what lives in HubSpot, what lives elsewhere, and what (if anything) needs to sync between them.
5. Name your fields consistently from the start. If you create a custom field, give it a clear name and write a one-line note about what it means. Having two fields called "Lead Source" and "Contact Source" that mean the same thing sounds minor — until you're trying to build a report six months later.

Phase 2: Define Your Lifecycle Stages

This is the step most first-time HubSpot users skip. It's also the one that breaks the most things later. If your lifecycle stages aren't defined, your automations won't know when to fire.

6. Write down what each stage means for your team. Don't just accept HubSpot's default definitions. Write one sentence for each stage that describes exactly when a contact reaches it. "An MQL is someone who has requested a demo or downloaded more than two resources" is a definition. "Someone who seems interested" is not.
7. Write down what moves a contact from one stage to the next. What action or event turns a Lead into an MQL? What makes an MQL become an SQL? Document this before you build anything. Automations move contacts between stages — but they can only do that if you've told HubSpot what the rules are.
8. Test it manually before you automate it. Create a fake test contact. Manually move it through each stage yourself. Does everything look right? Twenty minutes of manual testing now catches problems that would otherwise take hours to track down later.

Phase 3: Set Up Your Sales Pipeline

9. Keep your deal stages to 4–6. Most B2B companies need four to six stages. Something like: New, Discovery Done, Proposal Sent, Negotiating, Closed Won / Closed Lost. If you find yourself adding more and more stages, ask whether each one is tracking where the buyer is, or just logging what your rep did last. Log activities in notes — not pipeline stages.
10. Add a win probability to each stage. Each stage has a "close probability" field — basically, what percentage of deals at this stage eventually close. You don't need exact numbers on day one. Rough estimates are fine. These feed into your revenue forecast, so having something is better than leaving them blank.
11. Set required fields so deals don't move forward with missing information. Decide what a rep has to fill in before a deal can move to the next stage. At minimum: company name and expected close date at the start, deal value before it gets to late stages. This is how you keep your pipeline data clean without manually checking every deal.
12. Set up your default pipeline view. When a rep opens their pipeline, what columns do they see? Make sure "Last activity" and "Close date" are visible by default. Small quality-of-life changes like this get your team logging in regularly.
13. Create two simple automations for your pipeline. First: notify the manager when a deal reaches a late stage. Second: create a follow-up task when a deal hasn't had any activity in a certain number of days. These two alone handle the most common pipeline management headaches.

Phase 4: Set Up Who Can See and Do What

Permissions feel like a boring admin task until someone accidentally deletes 200 contacts or a junior rep sees a deal they weren't supposed to. Set this up before anyone logs in.

14. Invite your team and assign roles before they start using HubSpot. HubSpot lets you control exactly what each user can view, edit, and delete. If your team starts using it before you've set permissions, you'll spend a day undoing things that shouldn't have been touched.
15. Make sure each team only sees their own pipeline. If you have a sales pipeline and a customer success pipeline, your sales reps don't need to see (or accidentally edit) the CS pipeline. Limit access by team.
16. Lock down sensitive fields. Things like contract value or discount approval probably shouldn't be editable by everyone. HubSpot Professional and above lets you restrict which roles can edit which fields. Use it for anything that could cause problems in the wrong hands.
17. Set up Teams now if you'll want team-based reports later. If you want to see performance by team (not just by individual), you need to set up "Teams" in HubSpot before you have data. It's difficult to apply retroactively.

Phase 5: Build Your First Automations

Don't try to automate everything at once. Start with four or five workflows that solve real problems. You can always add more later.

18. Build workflows that move contacts through your lifecycle stages. These are the automations that advance a contact from Lead to MQL to SQL based on the rules you wrote in Phase 2. Before turning any on, ask yourself: can the trigger condition actually happen in our setup? A workflow that fires when a contact becomes an MQL does nothing if contacts never actually reach MQL status.
19. Build a lead assignment workflow. If more than one sales rep handles inbound leads, set up automatic assignment now. Round-robin (rotating between reps evenly) is the simplest starting point. Without this, someone ends up manually assigning every lead by hand.
20. Build three notification workflows. One for when a form is submitted. One for when a deal reaches an important stage. One for when a contact's lifecycle stage changes. These three alone keep your team informed without anyone having to check HubSpot constantly.
21. Before turning on any workflow, trace exactly how a contact would enter it. Ask: what has to happen first for this workflow to trigger? Is that thing currently set up? A workflow that triggers on "lifecycle stage = Lead" fires zero times if nothing in your system ever sets anyone to Lead.
22. Turn workflows on one at a time. Wait a day or two between each one. Watch what happens. If something fires unexpectedly, you'll know exactly which workflow caused it. Turning everything on at once makes it impossible to diagnose problems.

Phase 6: Connect Your Other Tools and Build Reports

23. Connect your calendar and email first. This is the most important integration. Until your team's meetings and emails are showing up in HubSpot automatically, they have no reason to log in regularly. Get this done before anything else.
24. Connect any other tools before you go live. If HubSpot needs to talk to your billing system, your calendar tool, or anything else — set it up now. Connecting tools after months of real data exist is a much bigger project. Once your core setup is clean, the HubSpot AI tools guide covers which AI features are worth enabling at this stage.
25. Write one line about each integration. For each connected tool, note: what data goes in, what comes out, and which system wins if the same field has different values in both places. You'll need this the first time something syncs in a way you didn't expect.
26. Build 5–6 dashboards, not 20. A dashboard is just a collection of charts and reports on one screen. Build the ones your team actually needs: deals by stage, new leads by source, activity by rep, and whatever your manager asks about in meetings. You can add more as you learn what's useful.
27. Set who can see which dashboards. Not every rep needs to see everyone else's numbers. Decide on sharing settings before people start opening dashboards they weren't meant to see.

Phase 7: Test Everything Before You Go Live

Testing means actually putting a fake contact through the full experience, not just clicking around. There's no substitute for this step.

28. Create a test contact and walk it through every step. Fill out one of your forms as if you were a real prospect. Watch the contact get created. Move it through lifecycle stages. Create a deal. Advance it through the pipeline. Every workflow, email, and notification that should fire — does it? Every step that requires a field to be filled in — does it block you if the field is empty? This is the only way to catch things that are broken before your real customers find them.
29. Ask two people to use HubSpot for a full day before the team launch. Pick your two most thorough people and tell them to try to break things. They will find things you missed. That's the point.
30. Write down the things you decided not to build yet. Keep a simple list of features and automations that are planned but not live. This prevents the "wait, I thought we were setting that up" conversation that happens in month two of every implementation.

Four Things to Skip on Day One

These features feel important early on but almost always work better once you have real data and a team that's comfortable in HubSpot.

• Lead scoring. Lead scoring is a system that assigns points to contacts based on their behavior (opened 3 emails = 10 points, visited pricing page = 20 points). It's useful, but building it before you have real data is guesswork. Wait 90 days, see what your actual customers have in common, then build the model.
• Custom objects. Custom objects let you track things that don't fit into contacts, companies, deals, or tickets (like properties you've sold or products you've rented). Most small B2B companies never need them. If you're not sure whether you need custom objects, you probably don't yet.
• Every workflow you can think of. It's tempting to automate everything on day one. Don't. Start with five or six that solve real problems. Add more as your team runs into things they wish were automated.
• The full marketing setup. Email templates, subscription types, blog settings, landing pages — if your marketing team isn't going to use these in the next 30 days, leave them for later. A half-configured marketing setup causes confusion without adding value.

Frequently Asked Questions