When a HubSpot setup goes wrong, the cause is often in place before anyone logs in: no one owned the project, the data was never cleaned, or sales and marketing never agreed what a lead is. This checklist is weighted towards that early work, because it's the part teams skip and later regret.
Key takeaways
- A CRM implementation checklist for HubSpot has three parts: what to prepare before you start, what to build and test during the project, and what to keep doing after launch.
- Preparation matters most. Agree goals, name an internal owner, list your data sources and write down your current process before configuring anything.
- Clean and map your data before it goes into HubSpot, and test the import with the people who know that data.
- Don't go live until real users have tested the system and every role has been trained.
- After launch, schedule data health checks and workflow reviews; a CRM that isn't maintained slowly drifts away from how the business works.
Use this list alongside our CRM implementation roadmap, which explains each step and how long it typically takes.
Before implementation: preparation checklist
This is the longest section on purpose. Every item here is a decision that becomes slower and more expensive to make once the build has started.
Objective and ownership
- Write down the two or three business problems HubSpot must solve first (for example: missed enquiries, no view of the sales pipeline, reports assembled by hand).
- Agree how you'll measure success, such as response time to new enquiries, pipeline visibility, or hours saved on reporting.
- Name one internal CRM owner who will run the project day to day and look after HubSpot after launch.
- Name the person who makes final decisions when teams disagree.
- Set a realistic launch window. Most implementations take 4 to 12 weeks; plan for longer if you're covering several markets or many integrations.
- Agree the budget, including HubSpot subscription costs and any partner fees.
People
- List every team that will use HubSpot (marketing, sales, service, management, finance) and pick one representative from each.
- Note who will be an admin and who will be an everyday user. They need different training.
- Block time in calendars for discovery workshops, design reviews and testing. Projects stall when the people who know the process aren't available.
- Ask each team what frustrates them most about the current way of working. Their answers become your priorities.
Data sources
- List every place customer data lives today: spreadsheets, inboxes, website forms, an old CRM, accounting software, ecommerce platforms, staff notes.
- For each source, note who owns it, roughly how many records it holds and how up to date it is.
- Decide what moves into HubSpot and what stays behind. Old, incomplete or duplicate records don't need to come with you.
- Flag known data problems early: duplicates, missing email addresses, inconsistent company names, different formats for the same field.
Processes and definitions
- Write down how a new enquiry becomes a customer today, step by step, even if the process is informal.
- Agree shared definitions across teams: what counts as a lead, a qualified lead and a customer. These become your lifecycle stages.
- Map your sales stages from first contact to closed deal. These become your deal pipeline.
- Note the hand-off points between marketing, sales and service, and who owns the customer at each stage.
- List the reports leaders actually look at today, and the ones they wish they had.
Platform scope
- Decide which HubSpot products you need now and which can wait. HubSpot's current lineup is Smart CRM plus Marketing Hub, Sales Hub, Service Hub, Content Hub, Data Hub (formerly Operations Hub) and Revenue Hub (formerly Commerce Hub). You can start with one hub and add others later.
- Check that your subscription tier includes the features your process needs, such as workflows, custom reports or permissions.
- List the other systems HubSpot must connect to (see the integrations section below).
-
During implementation: build and test checklist
Design
- Turn your process notes into a CRM design: records (contacts, companies, deals, tickets), properties, lifecycle stages, pipelines, ownership rules and permissions.
- Keep required properties to the minimum each team needs. Every extra mandatory field slows down data entry.
- Review the design with each team's representative, ideally as a prototype or mockup rather than a list of field names.
- Get the design signed off before configuration starts.
Data migration
-
Clean the data before importing: remove duplicates, fix formats, fill or remove incomplete records. Our guide to
cleaning your HubSpot CRM data covers the details.
- Create a data mapping document showing where every field from each source goes in HubSpot.
- Run a test import with a sample of records.
- Have the people who know the data check the test results: are companies linked to the right contacts, are deals in the right stages, is anything missing?
- Fix the mapping, then run the final migration as close to launch as possible.
Configuration
- Set up users, teams and permissions.
- Build pipelines and deal stages, lifecycle stages and custom properties as designed.
- Create forms, and connect them to lead assignment rules so every new enquiry gets an owner.
- Build email, landing page and document templates in your brand.
- Set up workflows for the repetitive tasks you identified, such as lead rotation, follow-up tasks, lifecycle stage updates and lead nurturing.
- Build dashboards for the reports leaders agreed on during preparation.
- Keep the first version proportionate. Automate what must work at launch; add the rest once people are using the basics.
Integrations
Integrations connect HubSpot to the other tools your business runs on, so data flows between them instead of being re-entered by hand. Common examples include:
Salesforce:
sync records between the two CRMs so marketing and sales share the same data.
Mailchimp:
connect existing email marketing lists and campaigns with HubSpot contacts.
Slack:
send HubSpot notifications, such as new leads or deal updates, to the right team channel.
Shopify:
bring ecommerce customers and orders into HubSpot to track purchases alongside other interactions.
For each integration on your list:
- Confirm it supports what you need, either through a standard HubSpot connector or a custom build.
- Decide which system is the source of truth for each type of data, and which direction data flows.
- Test the integration with real records before launch.
- Note who will maintain it after go-live.
See HubSpot Integration for how Woven connects HubSpot with accounting, ERP, ecommerce, messaging and bespoke systems.
Testing
- Write test scenarios based on real tasks for each role: logging a new enquiry, moving a deal, handling a ticket, pulling a weekly report.
- Ask the actual users to run them (user acceptance testing, or UAT).
- Check that workflows fire correctly, emails go to the right people and reports show the right numbers.
- Fix the issues raised, and retest anything that changed.
Training
- Run separate sessions for admins and for each user group, focused on the tasks they'll do every day.
- Give everyone short reference material they can return to after the session.
- Schedule a follow-up session two to three weeks after launch, when the real questions appear.
Go-live readiness check
Before launch, you should be able to answer yes to each of these:
- The design has been signed off by every team that uses HubSpot.
- Final data has been migrated and spot-checked by people who know it.
- Integrations have been tested with real records.
- Every user has an account with the right permissions.
- Each role has been trained and has reference material.
- Users have tested their main tasks and the issues they raised are fixed.
- Forms, workflows and notifications have been tested end to end.
- The internal CRM owner knows who to call for help after launch.
- Old systems or spreadsheets that HubSpot replaces have a switch-off date.
If any answer is no, it's usually cheaper to delay the launch by a week than to fix the damage to trust afterwards.
After implementation: aftercare checklist
First few weeks
- Check daily that new records are being created and updated as expected.
- Watch for workarounds, such as people keeping their own spreadsheets, and ask why.
- Fix small issues quickly; early fixes build trust in the system.
- Run the follow-up training session.
First few months
- Run a data health check: duplicates, incomplete records, records without owners.
- Review each workflow: is it still doing what the process needs?
- Compare results with the success measures you agreed during preparation.
- Collect requests for new properties, reports or automations, and prioritise them.
Ongoing
- Schedule regular reviews of data quality, workflows and dashboards.
- Keep up with HubSpot product updates and decide which new features are worth adopting.
- Update training material when processes or features change, and train new joiners properly.
- Revisit your integrations whenever a connected system changes.
Where this fits
This checklist covers the tasks; the CRM implementation roadmap covers the order, timing and who does what. If you'd like a partner to work through it with you, Woven is a HubSpot Diamond Solutions Partner in Singapore offering HubSpot implementation services, built around our 3P framework of People, Process and Platform.