How a HubSpot implementation for manufacturers runs, start to finish
This page covers the project itself. You'll see where it starts, who you need on your side, what happens at each stage and where manufacturing rollouts usually go wrong.
Free, 30 minutes, and you'll leave with at least one clear next step.
Where does a manufacturing HubSpot implementation start?
It starts from one of three places, and each one changes the plan. You're moving off Salesforce or another CRM. You already have HubSpot and the team doesn't trust it. Or your sales team runs on spreadsheets and email.
We've done the first two for manufacturers. A custom power systems manufacturer had already tried once to move off Salesforce, and that attempt left gaps and fields that didn't match. A commercial oven manufacturer had a HubSpot account full of stale deals and uncalled leads. Spreadsheet starts are simpler in one way, since there's no old system to untangle. Most of the effort goes into the pipeline and cleaning up the history you bring in.
If you want to know what HubSpot does for a plant's sales team once it's running, see HubSpot for manufacturing. This page is about getting there.
Moving in, or fixing what you have
The first two starting points need different first steps.
Moving from Salesforce or another CRM
- List the custom fields and reports people actually use
- Merge duplicate fields before anything moves
- Spot-check records after each load
- Set a date to make the old system read-only
Rebuilding a HubSpot account you don't trust
- Audit the whole account before changing anything
- Close out dead deals so the forecast shrinks to the truth
- Pull every lead that hasn't been called
- Rebuild pipelines with required fields
Five stages, with your sign-off at each one
Each stage ends with something you can check before we move on.
Stage 1: Agree the scope and the first team
Who decides, which division goes first and which reports managers need on day one.
We meet your project owner, sales leaders and the person who runs the ERP. Together we pick the first team to go live, list the reports managers use today, even if they're in Excel, and follow a few recent quotes to order. You get a written scope and a plan.
You get A signed scope and a list of launch reports.
Stage 2: Move your data in cleanly
Contacts, companies and deals come over with duplicates merged and records spot-checked.
We map every field from the old system to HubSpot, merge duplicate fields and drop dead ones. After each load we spot-check records, and sales leaders check a sample of their own accounts before we call it done.
You get Clean data in HubSpot, checked by your team.
Stage 3: Build the sales process in HubSpot
Stages, required fields, assignment rules and alerts for deals that stall.
We map your sales process stage by stage, including engineering reviews and approvals. Reminders, assignment rules and stalled-deal alerts replace manual steps. Every rep follows the same stages from first inquiry to order.
You get A working pipeline your managers have approved.
Stage 4: Connect HubSpot to the ERP
Customers and orders match in both systems, so reps stop keeping a side list.
We agree which system owns each record, then build or clean up the sync. For the power systems client, that meant reviewing and organizing an existing sync so customers and orders matched in both. If you run NetSuite, see our NetSuite integration page.
You get An ERP sync both teams trust.
Stage 5: Train each role and switch off the old way
Short training by role, dashboards for managers and a date the old system goes read-only.
Training covers what changes in each person's day, not every button. The power systems team had three sessions plus deal and rep activity dashboards. The oven maker got eleven short videos, so new reps learn the same process later.
You get A trained team, live reports and one system of record.
Who you need on your side
An implementation goes as fast as your people can make decisions. These are the roles we ask for.
- A project owner who can settle arguments about the sales process.
- Your best rep and your newest rep, to test the setup before launch.
- The person who knows how your ERP stores customers and orders.
- An applications engineer, if quotes need engineering input.
- A sales manager who will open the reports every week after launch.
Where manufacturing rollouts go wrong
We see these on rescue projects more than any others.
The old mess moves in
Forgotten custom fields come across, and the new system is confusing on day one.
Engineering is left out
Quotes wait on engineering, but there's no stage for it. Managers can't see where deals sit.
No switch-off date
The old CRM stays open, so reps keep using it, and you pay for two systems that both look half right.
Training happens once
New hires learn from whoever sits next to them. Short recorded videos keep the process the same a year later.
What changes when you're coming from Salesforce?
Most of the risk sits in the data. Look for custom fields, reports that depend on them, and records that exist twice. We sort those out before anything moves. Our Salesforce to HubSpot migration checklist lists what we check, and our Salesforce to HubSpot migration page covers the move for any industry.
Keep Salesforce read-only for a short time after launch so people can look things up, then retire it. The power systems client now works from one sales system tied to its ERP. Since leaving Salesforce, the company gets hours back every week.
Related work for manufacturers
Connecting HubSpot to your ERP
How the sync works and what to decide first.
How to connect HubSpot to your ERPQuoting in HubSpot
When quotes can be built in HubSpot and when they should stay in the ERP.
CPQ and quotesWhat an implementation costs
The factors that move the price, before you ask for a quote.
What a HubSpot implementation includes and how pricing worksA process review first
Our Friction Point Analysis starts with a paid initial analysis of 2 to 4 weeks. Its fee is credited toward work started within 60 days.
Friction Point AnalysisHubSpot implementation questions
How long does a HubSpot implementation take for a manufacturer?
It depends on the starting point. A rebuild of one sales team's pipeline is the shortest. A Salesforce move with an ERP sync takes longest. Your written scope spells out the timeline.
Should we fix our data before or during the HubSpot move?
During. We clean as we map, merging duplicates and dropping dead fields, so you don't pay to move problems into the new system.
What happens to our Salesforce reports when we switch?
We list the reports managers use and rebuild those in HubSpot. The rest get left behind.
How do we get engineers to log their part of a deal?
Give them a task with a due date and one or two fields to fill in, nothing more. When engineering review is a pipeline stage, managers can see where deals wait.
Which HubSpot hubs does a manufacturer usually need?
Sales Hub for the sales team in almost every case. Marketing Hub if you run campaigns, and Service Hub if you track service requests. We size it on the first call.
Can we roll HubSpot out to one division first?
Yes, and it's often wise. One team proves the setup, then the next team starts with fewer surprises.
Related
More in Manufacturing
Show us how a quote moves today
Bring your current CRM or spreadsheet. We'll tell you which starting point you're at and what the first stage would cover.