Manufacturers track an installed base in HubSpot by creating an equipment record for each serial number, associating it with the owning company, the site, the product, and the service contract, and calculating warranty and service dates on the record. Workflows then turn those dates into tasks and parts or service deals, while the ERP and any field service tool stay the systems of record for orders, serial numbers, and work orders.
A machine leaves the plant with a serial number and stays in service for years. The parts, service, and upgrade revenue it generates depends on knowing where it is, who owns it, and when it needs attention next. When serial numbers sit in systems the account team never opens, every parts or service conversation starts from scratch.
This guide covers what each equipment record holds, how units connect to owners and sites, where serial numbers come from, which dates drive outreach, and how service contracts and tickets attach to each unit.
Manufacturers track an installed base in HubSpot with an equipment record for every serial number, linked to the account, the site, and the service contract, with its key dates calculated on the record. Reps see every unit on the account page and act on the next date.
The installed base drives parts and service revenue because every unit in the field needs maintenance, spares, and eventually an upgrade or replacement. Each of those sales starts with knowing the unit, its owner, and its next date.
BCG's 2025 research on aftermarket services for industrial manufacturers found that services carry gross margins about twice the 15% to 25% typical of equipment sales, and that spare parts and consumables average gross margins of 50%. It also notes that some manufacturers underperform in services because they lack information about installed equipment, including its condition, location, usage, and service history.
The ERP owns products, BOMs, orders, and shipments, the field service tool owns work orders and technician history, and HubSpot owns the account-facing equipment view and the dates that drive outreach. Each system keeps the data it handles best.
| Data | System of record | What HubSpot holds |
|---|---|---|
| Products, BOMs, and parts catalogs | ERP | Model and SKU on the equipment record |
| Orders, invoices, and shipments | ERP | Ship date, bill-to, and ship-to on the unit |
| Work orders and technician notes | Field service tool | Last service date and a link to the work order |
| Equipment record and owner | HubSpot, seeded from the ERP | The full account-facing view |
| Warranty, service, and renewal dates | HubSpot, calculated from source dates | Dates that drive tasks and deals |
| Parts, service, and upgrade deals | HubSpot | Deals tied to the unit |
Our guide on when HubSpot should be your system of record covers this split in more depth.
An equipment record should hold the serial number, model, key dates, status, configuration, and service timing for one unit. On Enterprise, a custom object holds one record per serial number, and company properties work for manufacturers with only a few units per account.
The core fields come from three places. From the ERP: serial number, model and SKU, ship date, and a configuration summary such as voltage and options. From commissioning or field service records: install date, firmware or revision, last service date, and run hours where available. HubSpot calculates or maintains the rest: warranty start and end dates, next service due, a status of In service, Transferred, or Decommissioned, and an owner confidence value of Confirmed, Likely, or Unknown.
An equipment custom object fits accounts with many units, units that move between sites, and per-unit reporting, with more setup and more records to maintain. Company properties work on any tier when each account has only a few units, though one set of values per company blurs the detail of individual units.
HubSpot's guide to creating custom objects notes they need an Enterprise subscription. Record and custom object limits depend on your subscription, and HubSpot's guide to tracking CRM data limits shows where to check usage. Start with the custom object when units carry their own dates. Our technology consulting team can help you size the model.
Who owns it: the aftermarket or service operations lead.
Sign it's working: every unit shipped in the last year has an equipment record with a serial number, model, and ship date.
Associate each equipment record with the owning company, the site where it runs, the product, the selling dealer or distributor, and the contacts who maintain it, using labels that name each role. Reps then see every unit from the account and every relationship from the unit.
Use labels on the equipment-to-company association for Owner (who owns it today), Bill-to (who was invoiced), Site (where it runs), and Sold by (the dealer or distributor). Label contacts by role, such as Maintenance lead, Operator, and Purchasing. Associate each unit to its service contract, deals, and tickets as well.
Per HubSpot's guide to creating and using association labels, custom labels need a Professional or Enterprise subscription, and each object pair holds up to 50 labels. Model multi-site customers as a parent company with sites as child companies, or as a Site property on the equipment record when sites don't need their own records.
The bill-to is the company invoiced for the unit, from the ERP invoice. The ship-to is where the unit was delivered, from the ERP shipment. The owner is who owns and operates the unit today, from a registration, dealer report, or commissioning record. These three often differ. A distributor may be invoiced, a job site may receive the unit, and an end customer may own it. Keep each as its own association so a later transfer changes only the owner.
Who owns it: sales operations, with owner updates from the aftermarket team.
Sign it's working: every active unit has an Owner and a Site association.
The installed base connects nine kinds of records. Use this table as the build plan.
| Record | What it holds | Key associations | Example properties |
|---|---|---|---|
| Equipment (custom object) | One serial-numbered unit | Owner, site, selling dealer, contacts, service contract, deals, tickets | Serial number, model, ship and install dates, status, warranty dates, next service due, owner confidence |
| Owner company | The company that owns the unit | Equipment, contacts | Industry, region, account owner |
| Site (child company) | Where the unit runs | Parent owner, equipment | Address, site code |
| Dealer or distributor (company) | The partner that sold the unit | Equipment with a Sold by label | Territory, partner type |
| Contact | People who maintain, operate, or buy for the unit | Equipment with role labels | Role, email, phone |
| Service contract | Coverage terms | Covered units, owner company | Contract type, start date, renewal date |
| Product (product library) | The model | Matched by SKU | SKU, product line |
| Deal | A parts, service, or upgrade sale | Equipment, owner company | Deal type, amount |
| Ticket | A service request | Equipment, contact, order | Category, warranty status at open |
Want a second look at your installed base model? The Architecture Blueprint maps your current HubSpot setup against where it needs to be, including the equipment records and associations behind aftermarket reporting.
Serial numbers come from ERP shipments, field service tools, registration forms, dealer reports, and commissioning records, and they reach HubSpot through an ERP sync, scheduled imports, or form submissions. The serial number is the matching key for every route.
Six routes bring serial numbers in: a HubSpot-built ERP data sync (native integration), an app listed on the HubSpot App Marketplace for your ERP or field service tool (marketplace app), an integration platform that moves serial-level data on a schedule (middleware), a regular export of shipped serial numbers (scheduled import), a registration form owners fill in, and code that reads ERP or field service APIs (custom API connection).
HubSpot's guide to using its integration with NetSuite lists companies, invoices, orders, and products among the synced objects, so serial-level equipment records usually need their own route. Our NetSuite and HubSpot integration, powered by Commercient middleware, offers another route. Confirm any field service tool connection on the HubSpot App Marketplace and in the vendor's documentation before you plan around it.
Store the serial number in a property that requires unique values, so a second load updates the existing unit. HubSpot's guide to setting validation rules for properties covers unique value properties, configured when the property is created. Send rows with missing or malformed serial numbers to an exceptions file with a named owner.
When historical units need cleanup before the first load, the same mapping and validation steps apply as a HubSpot data migration.
Who owns it: the ERP owner, with the HubSpot admin maintaining the load.
Sign it's working: each month's shipped serial numbers appear as equipment records within a day of shipment.
Find the owner of a channel-sold unit through registration, dealer and distributor reports, commissioning visits, and service tickets, and record how sure you are with an owner confidence property. Units sold through distributors often start with an unknown end customer.
A workflow can create a task for the channel manager when a unit has stayed Unknown for 60 days after shipment. Every service ticket is a chance to confirm the owner, so add an Owner confirmed checkbox to the ticket form technicians use.
Who owns it: the channel manager for distributor-sold units.
Sign it's working: the share of Unknown units falls each quarter.
When a unit changes owners, move the Owner association to the new company and keep the history. When a unit retires, set its status to Decommissioned so it leaves active reports and outreach.
Set the status to Decommissioned and record the date and reason. Keep the record, its tickets, and its deals, so lifetime revenue by unit stays intact.
Who owns it: the aftermarket team.
Sign it's working: decommissioned units drop out of service reminders, and transfers show both owners in the history.
Five dates drive installed base outreach: warranty end, next service due, contract renewal, run-hours intervals, and age-based upgrade windows. Calculate each on the equipment record, and let workflows turn them into tasks and deals ahead of time.
HubSpot's guide to creating calculation properties notes that custom equations can return dates and that Time until properties count down to a date. Calculation properties need a Professional or Enterprise subscription. Per HubSpot's guide to creating workflows, workflows need a Professional or Enterprise subscription.
These timings are examples to adapt to your products and contracts.
| Trigger | Date or interval | Action | Owner | HubSpot tool | Resulting deal or ticket |
|---|---|---|---|---|---|
| Warranty ending | 90 days before warranty end date | Offer a service contract | Aftermarket rep | Workflow, task | Service contract deal |
| Preventive maintenance due | 30 days before next service due | Email the maintenance lead and create a scheduling task | Service coordinator | Workflow, email, task | Service ticket |
| Contract renewal | 120 days before renewal date | Open a renewal | Account manager | Workflow | Renewal deal |
| Run-hours interval, where synced | Run hours pass the service interval | Offer a parts kit | Parts sales | Workflow, task | Parts deal |
| Upgrade window | Unit reaches its typical upgrade age | Start a replacement or upgrade conversation | Account manager | Workflow, task | Upgrade deal |
| Unknown owner | 60 days after shipment with no confirmed owner | Ask the distributor | Channel manager | Workflow, task | None |
Each model points to its recommended spares and consumables from the ERP's parts lists. Keep BOMs and parts catalogs in the ERP, and show a Recommended parts kit property on the equipment record so the rep knows what to offer when a trigger fires.
Who owns it: the aftermarket lead, with timings agreed with service.
Sign it's working: reps open parts and service deals before each date, with no spreadsheet lookups.
A CRM should track field service and maintenance contracts as records tied to each covered unit, with tickets that carry the unit, the order, and the warranty status. The field service tool keeps the work orders, and HubSpot keeps the coverage, the renewal, and the customer conversation.
Track each service contract as its own record, a custom object on Enterprise, with contract type, start date, renewal date, and covered units. Associate it to every equipment record it covers and to the owner company. A unit with no Covered unit association shows up in the uncovered units report.
Associate every service ticket with the equipment record, the order, and the contact. Copy the warranty status and contract coverage onto the ticket when it opens, so agents see coverage at a glance. Teams building a full service process can use HubSpot Service Hub for routing, pipelines, and SLAs.
HubSpot's guide to setting up a support portal covers the support portal on Service Hub Professional and Enterprise, where customers log in to view and reply to their tickets. Per HubSpot's guide to managing support portal settings, you choose which ticket properties customers see, so serial number, model, and site can appear beside each ticket. Customers can view tickets associated with their contact, or with their company as well.
Custom objects, workflows, the support portal, and standard integrations cover installed base tracking for most manufacturers. When serial-level ERP sync needs unusual transformations, run hours stream in from IoT or meter data, or customers need an asset portal with its own interface and permissions, Brainstem Ventures by Campaign Creators adds custom capabilities that connect to your existing systems. It's a specialized software engineering capability within Campaign Creators, built to keep the systems that work and engineer what's missing.
Who owns it: customer service, with contracts owned by the aftermarket team.
Sign it's working: every covered unit links to an active contract, and agents never ask for a serial number already on file.
Six reports show the health of an installed base: units in service by model, age, and region, units under contract, warranty expirations, aftermarket revenue by unit and account, and units with no known owner.
Reports that combine equipment, companies, and deals use HubSpot's custom report builder, available on Professional and Enterprise subscriptions. When your team wants help keeping these reports current, ongoing HubSpot support covers report fixes and new views.
Give the equipment record one owner, require key fields at creation, and check each month that shipped serial numbers match equipment records. Small gaps grow fast once reps rely on the data.
Manufacturers track an installed base in HubSpot with an equipment record for every serial number, associated with its owner, site, product, dealer, contacts, and service contract. Warranty and service dates calculate on the record, workflows turn them into tasks and parts or service deals, and tickets carry the unit for every service request. The ERP and field service tool keep orders, BOMs, and work orders, and HubSpot gives the account team a view of every unit they can sell against.
Campaign Creators designs HubSpot around accounts, products, orders, and installed assets for manufacturers that run on HubSpot and sell through reps, distributors, and dealers. As a HubSpot Elite Solutions Partner, we apply CRM architecture expertise to how equipment makers earn after the first sale.
We map your serial number sources, implement the equipment and service contract model in HubSpot, connect your ERP through our HubSpot integration library or HubSpot integration development, and build the triggers and reports your aftermarket team uses each week.
Before you add equipment records, a HubSpot Portal Audit shows where your current portal stands.
Ready to turn your installed base into parts and service revenue? Book a consultation with our team.