Setting up HubSpot for a Japan team: don't merge lifecycle stage and deal stage
When a global SaaS company stands up HubSpot for its new Japan team, someone usually asks for “one clean funnel from inquiry to closed won.” The local team is small, the request sounds efficient, and lifecycle stage and deal stage get merged into a single sequence.
Weeks later, the pipeline counts HQ reads no longer match reality, and automated emails go out to accounts that already lost.
Lifecycle stage and deal stage look alike, but they are different measures. Merge them and your reporting and your automation break at the same time.
Why this happens specifically in Japan entry
The failure is not unique to Japan, but three conditions make it more likely at market entry.
The Japan team is new and has no HubSpot administrator of its own, so the model is copied quickly from a template.
HQ wants Japan’s numbers to roll up into the same global dashboard, so there is pressure to force one shared funnel.
And Japanese deals run long, with an internal approval stage that Western pipelines do not model, so accounts sit in the middle for months while someone tries to “keep the funnel moving” by advancing the lifecycle by hand.
Under those conditions, collapsing the two axes feels like the tidy choice. It is the one that quietly poisons the data HQ uses to judge the market.
The distinction, and the decision
Lifecycle stage is a property on the contact and the company. By design it moves forward and does not roll back.
Deal stage lives on the deal and moves through a pipeline, and one company can hold several deals at once.
One axis is the state of the customer; the other is the progress of an opportunity. Different objects, different direction of travel.
The decision is to keep them fully separate.
Drive lifecycle stage by automation from clear conditions, and let the sales team move deal stage by hand.
Do not let a human maintain both, because when a deal is lost the contact’s lifecycle will stay at “customer” unless someone remembers to reverse it, and at market entry no one does.
Anything a rule can determine should not be typed by a person.
What it means for the numbers HQ sees
Keep the two axes apart and Japan’s counts start matching reality, which is the whole point when headquarters is deciding how much to invest in the market.
In HubSpot Japan’s 2024 survey (n=1,545, a vendor study by HubSpot, which sells CRM), 79% of respondents reported some difficulty using their data, and 24.4% cited poor data connection across departments.
Merging lifecycle and deal stage recreates exactly that disconnection inside the CRM: marketing’s “state of the customer” and sales’ “progress of the deal” are jammed into one column, and neither number can be trusted.
The generalizable rule is single. Design the state of the customer and the progress of the deal as two separate axes.
One merged funnel looks neater on screen, but because one axis can never move backward, your denominators drift and your automation fires on the wrong conditions.
Two correct pipelines beat one tidy one, especially when HQ is reading the result from the other side of the world.
Related reading
Once stages are separated, the next thing that stops reconciling is the denominator. Start with the denominator covers how to align it with HQ.
Other notes on the same problem are collected under CRM adoption.