Category: HubSpot CRM Setup

  • HubSpot Sequences vs. Workflows: What’s the Difference?

    HubSpot workflows are system-level automation: they run on criteria you set, work across contacts, companies, deals, and tickets, and can branch, delay, and update records. HubSpot sequences are rep-level outreach: a series of one-to-one emails and tasks sent from a rep’s own inbox to one prospect, which stops automatically when the prospect replies or books a meeting. The fastest test is to ask who the message is from and whether it should stop when a human responds.

    Teams often use one tool for both jobs and get poor results. Nurture emails sent as a “sequence” don’t scale. Sales follow-ups built as a “workflow” feel like marketing blasts and keep sending after the prospect has answered. This guide explains the difference, shows when to use each, and shows how to combine them without sending a prospect two competing messages.

    The differences at a glance

    Dimension Sequences Workflows
    Purpose One-to-one rep outreach One-to-many operational and marketing automation
    Owner The rep or sales team RevOps, marketing, or operations
    Sender The rep’s connected inbox A shared or system address
    Trigger Rep enrollment, with limited auto-enrollment by plan Forms, property changes, page visits, deal stage, and more
    Logic Linear steps: emails and tasks with delays Branching, delays, and conditions
    Works on Contacts Contacts, companies, deals, tickets, and other objects
    Email type One-to-one business email Marketing email with subscription rules
    On reply Unenrolls on a genuine reply or a booked meeting Continues according to its own logic
    Other actions Tasks for the rep Set properties, rotate owners, create tasks, send internal notifications, and more

    Sequences are built for a person writing to a person. Workflows are built for a company’s systems acting on records. A third difference is where replies go. A reply to a sequence email lands in the rep’s inbox and is tracked in HubSpot, while a reply to a marketing email goes to the reply-to address, which HubSpot isn’t connected to, so that reply isn’t tracked.

    Which one should you use? Ten scenarios

    Scenario Use Why
    Nurture emails to hundreds of MQLs Workflow Marketing email at scale, with subscription handling
    A rep following up after a demo Sequence Personal, from the rep, and stops on reply
    Assign an owner and create a task when a form is submitted Workflow It updates records and routes work
    Outbound to a prospect list Sequence One-to-one outreach with calls and tasks mixed in
    Update lifecycle stage when criteria are met Workflow Property automation, no email involved
    Notify the team when a deal reaches a stage Workflow Internal notifications and tasks
    Webinar follow-up to all attendees Workflow Bulk, branded, and trackable as marketing
    Personalized follow-up after a meeting Sequence It should read like a person wrote it
    Re-engage stalled deals Workflow plus sequence The workflow finds the deals and creates tasks, and a rep sequence does the outreach
    Renewal reminders from a CSM Sequence or workflow task Use a sequence if the CSM sends it personally, and a workflow if the task is internal

    Three questions settle most cases. Is it one-to-one or one-to-many? Should it stop when the person replies? Does it need to act on records, such as changing a property or creating a deal? If you answer “one-to-one, yes, no,” build a sequence. If you answer “one-to-many, no, yes,” build a workflow.

    Using them together: a worked flow

    The strongest setups assign each tool its natural job. Here’s a common pattern for inbound leads.

    Step Tool What happens
    1. A prospect submits a demo form Workflow Sets lifecycle stage and lead status, assigns the owner, and creates a task with a due date that matches your SLA
    2. The rep reviews the lead Sequence The rep enrolls the contact in a short sequence of personal emails and call tasks
    3. The prospect replies or books a meeting Sequence The contact is unenrolled automatically
    4. A meeting is booked Workflow Creates the deal, updates the lifecycle stage, and notifies the account team
    5. The sequence ends with no reply Workflow Updates lead status, moves the contact into marketing nurture, and logs the outcome

    This keeps the personal outreach with the rep and the record keeping with the system. For the pieces around it, see our guides to lifecycle stages, the sales and marketing SLA, and AI tools for lead handoff.

    Plans, seats, and limits

    Topic Sequences Workflows
    Subscription Sales Hub or Service Hub Professional or Enterprise Available across Hubs; sending marketing email from a workflow needs Marketing Hub Professional or Enterprise, with some Service Hub options for service emails
    Seats and setup An assigned paid seat, sequences permissions, and a connected personal inbox Workflow permissions; no personal inbox required
    Daily sending Per-user daily limits, reported as 500 on Professional and 1,000 on Enterprise over a rolling 24 hours Email volume scales with your Marketing Hub contact tier
    Automatic enrollment Professional supports limited auto-enrollment set up inside a sequence The “enroll in sequence” and “unenroll from sequence” actions are Enterprise-only
    One at a time A contact can be in one sequence at a time A contact can be in many workflows

    HubSpot changes tiers, limits, and step counts regularly, and published guides don’t always agree, so confirm current numbers in HubSpot’s knowledge base before you design around them. If your plan lacks the workflow-to-sequence action, a practical workaround is to let the workflow create a task for the owner, who then enrolls the contact in a sequence.

    Stop sales and marketing automation from colliding

    The most common failure isn’t picking the wrong tool. It’s running both on the same person. A prospect gets a marketing nurture email on Tuesday and a personal sequence email on Wednesday, each unaware of the other.

    Collision Fix
    A contact is in a marketing nurture and a sales sequence at once Add enrollment exclusions so nurture workflows skip contacts who are in an active sequence, using the available “currently in a sequence” filter or a property you maintain
    A contact in an open deal still gets cold nurture Exclude open-deal contacts from top-of-funnel workflows
    A rep enrolls someone who has unsubscribed or opted out Check subscription and consent status before enrollment and apply your policy consistently
    Nobody knows which automation sent what Keep a shared inventory of workflows and sequences with owners and purpose
    Duplicate records create duplicate enrollments Clean duplicates first, as in our guide to clean CRM data

    Email law and consent rules apply to both tools, and the right approach varies by country, so have your legal counsel confirm what applies to your outreach.

    Building both well

    • Sequences: keep them short, mix emails with call or LinkedIn tasks, personalize the first line, and write each email to stand alone. For where AI helps and where it hurts, see our guide to AI sales email drafting.
    • Workflows: define the enrollment criteria and the goal first, add re-enrollment rules deliberately, and test with a few records before turning it on. Our workflow explainer covers the basics, and designing RevOps workflows covers the process side.
    • Both: write the process down before you build, name an owner, and review performance monthly.

    How to measure each

    Tool Metrics
    Sequences Reply rate, meetings booked, performance by step, and how many contacts finish without responding
    Workflows Enrollment, goal completion, conversion to the next lifecycle stage, and email engagement
    Both together Time to first touch, meetings per lead, pipeline created, and lead-to-opportunity conversion

    Tie these back to outcomes using closed-loop reporting, so you can see which automation produces pipeline and not just opens.

    Mistakes to avoid

    • Using sequences for mass nurture, then hitting daily send limits
    • Using workflows for rep outreach that should stop when someone replies
    • Letting prospects sit in marketing nurture and a sales sequence at once
    • Skipping unsubscribe and consent checks before enrollment
    • Building automation without owners, so nobody knows what is running
    • Assuming workflow-to-sequence enrollment is available on every plan
    • Measuring opens instead of replies, meetings, and pipeline

    Summary

    HubSpot workflows automate processes across records, with branching logic, property updates, and marketing email at scale. Sequences automate one rep’s outreach to one contact from the rep’s own inbox, and stop on a reply or booked meeting. Choose by asking whether the message is one-to-one or one-to-many, whether it should stop on reply, and whether it needs to act on records.

    The best setups combine them: a workflow routes the lead, a rep runs the sequence, and a workflow handles what happens next. Confirm plan, seat, and limit details with HubSpot, exclude contacts from overlapping automation, check consent before enrolling, and measure replies, meetings, and pipeline instead of opens.

    FAQ

    What is the main difference between HubSpot sequences and workflows?

    Sequences are one-to-one outreach from a rep’s inbox that stops when the prospect replies or books a meeting. Workflows are system automation across records that can branch, update properties, and send marketing email at scale.

    Which HubSpot plans include sequences?

    Sales Hub Professional and Enterprise, and Service Hub Professional and Enterprise. A paid seat, sequences permissions, and a connected personal inbox are required. Confirm current details with HubSpot.

    Can a workflow enroll a contact in a sequence?

    Yes, on Sales Hub or Service Hub Enterprise, using the “enroll in sequence” action, and the sender needs a paid Enterprise seat. On lower plans, a workflow can create a task for a rep to enroll the contact.

    Do sequences stop when someone replies?

    Yes. By default, a contact is unenrolled when they reply or book a meeting. Workflows don’t do this automatically, so you have to build the logic yourself.

    Can a contact be in a sequence and a workflow at the same time?

    Yes, but it often causes double messaging. Add exclusions so marketing nurture workflows skip contacts who are in an active sequence or open deal.

    Are there limits on how many emails a sequence can send?

    Yes. Sequences have per-user daily sending limits, reported as 500 on Professional and 1,000 on Enterprise, and limits on steps and enrollment. Workflow email volume depends on your Marketing Hub contact tier. Check HubSpot’s current limits.

    Which should I use for cold outbound?

    A sequence, since it’s personal, comes from the rep, mixes emails with call tasks, and stops on reply. Make sure you have a lawful basis and consent where required, and have counsel confirm your approach.

    Should marketing or sales own these tools?

    Sales usually owns sequences and marketing or RevOps owns workflows, but one team, usually RevOps, should keep an inventory of both so they don’t collide.

  • How to Choose a HubSpot Partner: 12 Questions to Ask Before You Sign

    To choose a HubSpot partner, define your scope first, use tier, accreditations, and directory reviews to build a shortlist, then decide using questions about people, process, pricing, ownership, and results. A partner’s tier tells you about its HubSpot business volume and retention. It doesn’t tell you whether it’s right for your project, your Hub, or your stage.

    Full disclosure: Revlyn is a RevOps consultancy that works with HubSpot, so weigh our view accordingly. This checklist applies to any partner you’re considering, including us.

    A bad partner choice is expensive in quiet ways: a portal nobody can maintain, workflows only the agency understands, and a second project to fix the first. This guide shows how to avoid that.

    Start with what you actually need

    Your need What to look for
    New implementation or onboarding A documented onboarding method and relevant accreditation
    Migration from another CRM Data migration experience, with a test and validation plan
    Custom integration Engineering capacity and API experience with your other systems
    RevOps strategy and process design Senior RevOps experience, beyond platform configuration
    Ongoing administration and optimization Capacity for a retainer, and response times in your time zone
    Training and adoption Role-based training and an adoption plan

    Write a one-page brief before you speak to anyone: goals, the Hubs involved, your current systems, timeline, budget range, and who on your side will own the work. If you’re moving from Salesforce, our migration checklist will sharpen the brief. If you’re weighing a partner against hiring, see RevOps consultant vs. in-house hire.

    What tiers, accreditations, and reviews tell you

    Signal What it tells you What it doesn’t
    Tier (Gold, Platinum, Diamond, Elite) HubSpot business volume. Diamond and Elite also carry a customer retention threshold, reported as at least 75% and 80% Whether they’re good at your project, Hub, or industry
    Accreditations Documented capability in a specific area, such as onboarding, data migration, or custom integration. A partner must be Platinum or above to apply Whether the people on your project are the ones who earned it
    Directory reviews Reviews tied to verified client engagements The full picture: partners tend to ask happy clients, and the directory is sorted by review count
    Individual certifications What specific people have learned How much real experience they have

    Thresholds and program rules change, and HubSpot restructured its partner program in 2026, so check the current requirements on HubSpot’s partner pages. Bigger isn’t always better. A top-tier agency may be best for large, complex projects, while a Platinum partner or a smaller specialist may give a mid-sized project more senior attention for the same money. Use tier to filter, not to decide.

    12 questions to ask before you sign

    Ask these on the first call, before any proposal, and note which ones get specific answers.

    # Question A good answer Red flag
    1 Which clients like us have you worked with, by size, stage, and Hub? Specific examples at similar scale Only large brands or generic claims
    2 Who will do the work, and what are their credentials? Named people, roles, and hours A senior pitch with junior delivery
    3 What will you ask about our setup before proposing? A discovery process and probing questions Ready to start building on the first call
    4 How do you document what you build? Solution design document, data dictionary, process maps “It’s all in the portal”
    5 How do you test and validate, especially migrations? Test batches, reconciliation checks, sign-off Cutover with no test plan
    6 How will you train us and hand over? Role-based training and recorded walkthroughs No handover plan
    7 How do you price the work? A clear model with assumptions and exclusions Vague estimates with no scope limits
    8 What happens when scope changes? A change process with estimates before work starts Surprise invoices
    9 Who owns the portal, credentials, and documentation? We do, from day one The partner holds the only admin access
    10 How do we exit if it isn’t working? Notice period, documentation handover, no lock-in Long minimum terms with no exit
    11 How will you measure success? KPIs tied to our goals, with a baseline and review dates Activity measures only, like hours or tasks
    12 Can we talk to references, including a project that got difficult? Yes, and an honest account of what went wrong and how it was fixed References only from the happiest clients

    Pay attention to question three. Good partners ask more questions than they answer in the first conversation. If they’re ready to build on day one, they’re selling, not diagnosing.

    Compare pricing models fairly

    Model Fits Watch for
    Fixed fee Well-defined projects such as a migration or implementation Scope disputes and change orders
    Retainer Ongoing administration and optimization Hours drifting with no outcomes attached
    Hourly or time and materials Uncertain scope Open-ended cost, so ask for an estimate and a cap
    Hybrid A fixed build followed by a retainer to run it A clear line between build and run

    Rates vary widely by partner type, seniority, and region, so published ranges are of limited use. Give three partners the same written brief and compare proposals line by line, including what’s excluded.

    Score the proposals

    A small scorecard keeps the decision honest. Our guide to SaaS solution scorecards explains the method in full. Here’s an illustrative example, scored 1 to 5, where the weighted total is the sum of weight times score divided by 5.

    Criterion Weight Partner 1 Partner 2 Partner 3
    Fit with our project and stage 30 4 5 3
    Process and documentation 25 5 3 3
    Commercial clarity 20 4 3 5
    The team assigned 15 4 4 3
    References and reviews 10 4 5 3
    Weighted total (out of 100) 100 85 79 68

    Set the weights before you read proposals, so they don’t bend toward the one you already like. If the top two are within a few points, run a small paid first phase to break the tie.

    Start small

    Before committing to a large project, consider a paid discovery or a small first phase, such as a data audit or one workflow rebuild. It shows how the partner communicates, documents, and handles surprises. Define a success metric, a deliverable, and a review date before it starts, and decide in advance what result would make you expand the work or stop.

    Red flags

    • Guaranteed revenue or ROI outcomes before any discovery
    • Pressure to buy more Hubs or a higher tier than your use case needs
    • Artificial deadlines on a proposal
    • Unwillingness to name the team, share sample documentation, or offer references
    • The partner keeping the only admin access to your portal
    • A proposal that could have been written for any company

    What the contract should include

    • Scope, deliverables, and what’s excluded
    • Milestones and acceptance criteria
    • Named roles and expected hours
    • Pricing, payment schedule, and the change process
    • Ownership and access: you hold the credentials and the documentation
    • Handover, training, and post-go-live support
    • Data protection and confidentiality terms
    • Notice and exit terms

    Have your legal counsel review the contract, especially data protection and termination clauses. This isn’t legal advice.

    Mistakes to avoid

    • Choosing on tier or brand alone
    • Starting without a written brief and a named internal owner
    • Reading testimonials on the partner’s own site instead of directory reviews and references
    • Skipping the question about who actually does the work
    • Signing a long term with no exit or handover
    • Letting the partner own your admin access and documentation
    • Comparing proposals on price without comparing scope

    Summary

    Choosing a HubSpot partner starts with a written brief that defines your scope. Use tier, accreditations, and verified directory reviews to build a shortlist, remembering that tier reflects business volume and retention, accreditations show documented capability, and reviews carry selection bias. None of them proves fit for your project.

    Decide using 12 questions on experience, people, discovery, documentation, testing, training, pricing, scope changes, ownership, exit, success measures, and references. Compare fixed, retainer, hourly, and hybrid pricing against the same brief, score proposals against weights set in advance, start with a small paid phase, and put ownership, handover, and exit terms in the contract.

    FAQ

    What do HubSpot partner tiers mean?

    They’re levels in HubSpot’s Solutions Partner Program, running upward from Gold to Platinum, Diamond, and Elite. They reflect a partner’s volume of HubSpot business, and the top tiers also require customer retention thresholds. They don’t prove fit for your specific project.

    Should I always pick the highest-tier partner?

    No. Higher tiers suit large, complex projects, but a smaller or mid-tier partner with relevant experience may give a mid-sized project more senior attention. Use tier to filter, then decide on fit, process, and references.

    Where should I look for reviews?

    On the HubSpot Solutions Directory, where reviews are tied to verified engagements, then ask for references directly. Read recent reviews that mention the Hub and type of project you’re buying, and remember partners usually ask satisfied clients to review them.

    How should I compare HubSpot partner proposals?

    Give each partner the same written brief, then compare scope, exclusions, named team, documentation, timeline, pricing model, and change process line by line. Score them against weights you set before reading any proposal.

    Should I hire a partner or a freelancer?

    It depends on scope and risk. A partner offers a team, documented methods, and continuity. A freelancer can suit a narrow, well-defined task. Either way, ask who does the work, how it’s documented, and who owns access.

    Who should own our HubSpot portal and credentials?

    You should, from day one. The partner can have admin access for the project, but you should hold super admin rights and receive the documentation. Put it in the contract.

    How do I avoid being locked in?

    Require documentation as a deliverable, keep your own admin access, avoid long minimum terms without an exit, and make sure workflows and properties are explained well enough for another team to maintain them.

    When is it time to switch partners?

    When you can name a specific, unresolved problem, such as missed deliverables, poor documentation, or a lack of senior attention. If the portal works and the relationship is healthy, switching to a higher-tier partner often costs more than it returns.

  • CRM modernization: What it is and why it matters

    CRM modernization is the work of updating a CRM’s data model, workflows, integrations, reporting, and adoption so it supports how a revenue team actually operates today, including AI-assisted work. It may involve a new platform, but it often doesn’t. The goal is a system people trust and can change quickly, not a newer logo.

    Most CRMs don’t fail suddenly. They accumulate. Someone adds a field for one campaign and never removes it. A workflow gets built by a contractor who has since left. Two integrations each write to the same property. A few years later, reports disagree, nobody wants to touch the automation, and reps keep a private spreadsheet because they don’t trust the system. Modernization is the process of reversing that drift.

    This guide explains what CRM modernization includes, how to tell whether you need it, the paths you can take, and a phased approach that avoids the most common mistakes.

    What CRM modernization is, and what it isn’t

    Modernization usually includes It does not automatically mean
    Simplifying the data model and retiring unused fields Buying a new CRM
    Fixing workflow friction and documenting automation Turning on every new feature
    Connecting systems so customer data flows reliably Moving data as it is
    Building clean, governed data that AI can use Adding an AI assistant on top of messy data
    Making the CRM useful enough that reps adopt it Training people on the old process

    A simple way to think about it is four layers, each of which can need work:

    Layer What changes Example
    Data Model, quality, and ownership Remove duplicates, standardize values, give each field one writing system
    Process and workflow Stages, routing, handoffs, and automation A written process spec, then a tested rebuild
    Architecture and integration Connections, syncs, and custom code Replace fragile point-to-point syncs
    People and governance Adoption, ownership, and change control A named owner, a data dictionary, and a review cadence

    Signs you need it

    What you see What it usually signals
    Reps keep spreadsheets alongside the CRM The CRM isn’t useful enough, or data isn’t trusted
    Sales, marketing, and finance report different numbers Inconsistent definitions or disconnected data
    Duplicate records and blank key fields everywhere Data quality debt
    Nobody dares touch a workflow Undocumented automation
    Integrations fail quietly Fragile architecture
    Custom fields no one can explain Technical debt in the data model
    New admins take months to get productive Complexity that has outgrown its documentation
    AI features produce weak or confusing output Data that isn’t ready for AI

    Technical debt in a CRM looks like legacy customization, inconsistent object models, fragile integrations, and automation nobody has documented. Each one slows change and raises the cost of every future project.

    Why it matters

    Trust in the numbers. Forecasts, pipeline reports, and renewal views are only as reliable as the data and definitions behind them. When leaders stop trusting reports, they stop using them, and decisions revert to opinion. Fixing the foundations supports everything from closed-loop reporting to forecasting.

    Speed and cost of change. A tangled system makes every request slow. A simple request, like adding a stage or changing routing, turns into a risky project. Modernization cuts the time it takes to ship a change and lowers the cost of maintaining what you have.

    AI readiness. Modernization guidance keeps returning to the same point: AI tools disappoint when the data underneath is inconsistent, duplicated, or locked in separate systems. Most of the work of becoming AI-ready is data work, and it’s better done before you add AI features than after.

    A connected customer view. Revenue teams need marketing, sales, billing, product, and support data on one customer record. If your CRM can’t hold that, workflows like renewal alerts and expansion signals can’t work. Our guide to the best CRM for integrating customer lifecycle data covers what that requires.

    Adoption and productivity. If entering data feels like a tax, reps skip it, and the quality problem gets worse. A modern CRM reduces manual entry and gives users something back, such as clear next steps and useful summaries.

    Governance and risk. Clear ownership, access controls, and documented data flows make privacy compliance, audits, and security reviews easier.

    Four paths, and when each fits

    Path What it means Fits when Main risk
    Optimize in place Clean data, simplify configuration, document and fix automation on your current CRM The platform can do the job but has accumulated debt Treating symptoms if the platform truly can’t support your needs
    Re-architect Redesign the data model, stages, and integrations on the same platform The structure is the problem, not the vendor Rebuilding without a clear process spec
    Re-platform Move to a different CRM A platform limit blocks revenue, or costs no longer scale Carrying old problems into the new system
    Consolidate Merge several CRMs or tools into one Different teams run separate systems with conflicting data Disagreements over definitions and ownership

    Many organizations can improve performance, usability, and scalability by modernizing the CRM environment they already own, so don’t assume modernization means a move. If you do need to change platforms, our Salesforce to HubSpot migration checklist covers the mechanics, and our buyer’s guide to B2B SaaS solutions offers a framework for deciding whether to optimize, extend, replace, or wait.

    A phased approach

    Most risk reduction happens during planning and auditing, not during the migration itself. A phased approach lets you prove value early and catch problems while they’re cheap.

    Phase Key outputs Success check
    1. Goals and baseline Business outcomes, a few baseline metrics, an executive sponsor Everyone can state what “better” means
    2. Audit Data quality findings, inventory of custom fields, workflows, and integrations, list of reports that can’t break, adoption review You know what exists and what depends on what
    3. Design Simplified data model, agreed definitions, stage and routing rules, ownership, governance A written spec that sales, marketing, and finance have signed off
    4. Clean and migrate Deduplicated, standardized data; migration or restructuring in a tested order Counts reconcile and a spot-check passes
    5. Rebuild automation and integrations Workflows and syncs rebuilt from the spec and tested with sample records Critical flows work, and failures raise alerts
    6. Adopt and measure Training tied to real tasks, feedback loops, dashboards Active use and field completeness improve
    7. Add AI where ready Targeted AI use cases on clean data, with human review Each use case has a metric and a stop rule

    Two phases deserve extra attention. Phase 4 begins with data cleanup, because migrating poor-quality data just relocates the mess. Our guide to cleaning up HubSpot data walks through that sequence. Phase 5 depends on a process spec, because recreating weak workflows in a new system keeps weak workflows. For maturity context, our RevOps maturity model can help you judge how much to attempt at once.

    How to measure whether it worked

    Outcome Example measure
    Trust in reporting Gaps between CRM, billing, and board numbers
    Data quality Duplicate rate and completeness of key fields
    Adoption Active users and time spent on data entry
    Speed of change Time to ship a routine change, such as a new stage
    Revenue process Time to first touch, forecast error, handoff quality
    Maintenance load Admin hours per week and number of undocumented automations

    Baseline these in phase one, then recheck at 30, 60, and 90 days after go-live. If the numbers haven’t moved, the project delivered a new system and not a modern one.

    Keep it modern: governance

    Without governance, a freshly cleaned CRM starts accumulating debt again within months. Name one owner for the system, maintain a data dictionary listing each important property’s meaning, owner, and allowed values, and put changes through a simple review. Add a data and automation review to your quarterly RevOps meeting cadence. If you lack the capacity in-house, our comparison of a RevOps consultant vs. an in-house hire can help you decide how to staff it.

    Mistakes to avoid

    • Choosing a platform first and figuring out the problem afterward
    • Migrating poor-quality data and expecting it to improve
    • Recreating weak workflows instead of redesigning them
    • Ignoring reporting continuity, so key reports break at go-live
    • Overlooking integrations, especially billing, product, and marketing syncs
    • Assuming adoption will follow without making the CRM useful to reps
    • Adding AI too early, before data and definitions are ready
    • Going big-bang with no pilot, no rollback plan, and no named owner

    Forecasting, reporting trust, adoption, and integration continuity are the areas that most often break during modernization, so give them explicit tests before go-live.

    Summary

    CRM modernization updates a CRM’s data model, workflows, integrations, reporting, and adoption so it fits how your revenue team works today. It may include a new platform, but often means simplifying and governing the one you have. It matters because it restores trust in reporting, speeds up change, prepares data for AI, connects the customer view across teams, and lifts adoption.

    Choose among four paths: optimize in place, re-architect, re-platform, or consolidate. Work in phases, from goals and baseline through audit, design, cleanup and migration, automation rebuild, adoption, and AI. Spend most of your effort on planning, data, and process, then govern the result with an owner, a data dictionary, and a regular review.

    FAQ

    What is CRM modernization?

    It’s the process of updating a CRM’s data model, workflows, integrations, reporting, and adoption so it supports how your revenue team works now, including AI-assisted work. It may or may not involve changing platforms.

    Is CRM modernization the same as CRM migration?

    No. Migration moves data to a different system. Modernization is broader and can happen on your current platform. A migration is one possible part of modernizing.

    When should we change platforms instead of optimizing?

    When a real platform limit blocks revenue or costs no longer scale, and you’ve confirmed the problem isn’t configuration, data, or process. Otherwise the same problems tend to follow you to the new system.

    How long does CRM modernization take?

    It depends on scope. Targeted optimization can take weeks, a standard migration often takes around six to eight weeks, and projects with custom objects, code, or many integrations take longer. Phasing the work lets you show results earlier.

    How do we prepare our CRM for AI?

    Clean and connect the data, agree on definitions, document workflows, and set governance first. Then add AI to specific use cases with a measurable outcome and human review.

    What breaks most often during modernization?

    Forecasting, trust in reporting, user adoption, and integration continuity. Test each explicitly before go-live and keep a rollback plan.

    Who should lead a CRM modernization project?

    Usually RevOps, with an executive sponsor and input from sales, marketing, customer success, finance, and IT. Whoever leads needs authority over definitions and the time to own the work.

    How do we keep the CRM modern afterward?

    Assign an owner, keep a data dictionary, review changes before they go live, and revisit data quality, automation, and integrations every quarter.

  • Customer Onboarding Workflows: How to Shorten Time to First Value

    A customer onboarding workflow is the repeatable sequence of steps, owners, triggers, and checkpoints that takes a new customer from signed contract to first value. Shortening time to first value (TTFV) means removing every step that doesn’t move the customer toward that first meaningful outcome, and automating the waiting, reminding, and handing off that slows everything else down.

    The deal closes, the celebration happens in Slack, and then nothing happens for two weeks. The customer success manager hasn’t been told what was promised, the customer’s admin is waiting for a kickoff invite, and the contract that was so urgent during the sales cycle sits unused. Those quiet weeks are where renewals are won or lost, because customers who don’t see value early start questioning the purchase.

    This guide shows how to define first value, find where onboarding time goes, design a workflow with clear triggers and owners, and measure whether it’s working.

    Start by defining “first value”

    First value is the first tangible result the customer cares about. It’s not “the kickoff happened” or “the account is configured.” Define it with the customer at kickoff, make it measurable, and pick one milestone per customer segment, so every early task points at it.

    Weak definition (an action) Stronger definition (an outcome)
    Admin logged in First live workflow running on real data
    Integration connected First report built from live data and shared with the sponsor
    Training completed Ten team members have completed their first task in the product
    Account configured The first invoice, ticket, or campaign processed end to end

    Time to first value is the number of days from signature, or from closed-won, to that event. It’s the headline metric for the rest of this guide.

    Where the days actually go

    Most teams assume onboarding is slow because setup is hard. Often the time goes to waiting. Here’s an illustrative breakdown of 52 days from closed-won to first value.

    Phase Days Who controls it
    Waiting for the handoff to reach the CSM 6 Us
    Scheduling the kickoff 8 Shared
    Data, integration, and security setup 21 Mostly the customer
    Configuration 7 Us
    Training 5 Shared
    Waiting on a stakeholder or a decision 5 The customer
    Total 52

    Only about a quarter of those days are hands-on work. The rest is handoff lag, scheduling, and customer-side readiness. That points to the highest-leverage fixes: capture the right information before the deal closes, trigger the handoff automatically, and get the customer’s technical prerequisites started in the sales cycle, not after it.

    Segment onboarding into tracks

    One onboarding model for every customer either overserves small accounts or underserves large ones. Most B2B teams define a small number of tracks, typically a high-touch track led by a CSM for complex accounts and a low-touch, largely self-serve track for the rest.

    Track Fits Touch model Core workflow
    High-touch Complex integrations, security reviews, many stakeholders Dedicated CSM or implementation lead Mutual success plan, weekly check-ins, project plan
    Mid-touch Moderate complexity Pooled CSM plus guided setup Kickoff call, checklist, scheduled office hours
    Tech-touch Simple setup, fast first value Automated, in-app guidance Triggered emails, in-app checklist, a help channel

    Assign the track from deal data, such as contract size, number of integrations, and security requirements, and record it on the deal so the workflow can route automatically. Set the thresholds from your own customers, since common ARR cut-offs vary widely.

    The onboarding workflow, stage by stage

    Stage Trigger Automated actions Human actions Exit criteria
    1. Handoff Deal moves to closed-won Create the onboarding project; notify the CSM; send a welcome message; require handoff fields Rep confirms commitments and stakeholders CSM has the full handoff packet
    2. Kickoff Handoff complete Send a scheduling link within a day; circulate a prework checklist Agree the first-value milestone, owners, and dates in a shared plan Mutual success plan signed off
    3. Setup Kickoff done Assign customer tasks; send reminders; flag blockers older than a set number of days Resolve technical and security issues Integrations live; data flowing
    4. Enablement Setup complete Role-based training invites; in-app guides; short videos Live training for key users Key users active
    5. First value Usage event fires Detect the milestone; notify the CSM; send a recognition message Confirm value with the sponsor Milestone confirmed and recorded
    6. Transition First value confirmed Start health scoring; schedule the first review Plan adoption and expansion Account moves to ongoing customer success

    Stage one is where onboarding is often won or lost. The handoff packet should carry stakeholders, the commitments made during the sale, success criteria, technical requirements, commercial terms, and any billing details. Our guide to quote-to-cash covers the contract and billing side of that handoff, and our piece on routing, handoffs, and pipeline hygiene covers tools that help.

    Automations that earn their keep

    Trigger Automation Owner
    Deal closed-won Create the onboarding record, assign the track, notify the CSM RevOps
    No kickoff scheduled within two business days Escalate to the CSM manager CS lead
    Customer task overdue by five days Send a reminder, then loop in the executive sponsor CSM
    No product activity for seven days after setup Alert the CSM and add the account to a stalled watchlist CSM
    First-value event detected Record the date, notify the team, and start health scoring RevOps and CS

    The timings above are examples to adapt. You can build most of this with CRM workflows, and many teams add an onboarding or implementation platform such as Rocketlane when projects get complex, plus in-app guidance for the tech-touch track. Whatever you use, make sure onboarding status flows back to the CRM so the whole revenue team can see a stalled implementation, not just the CS team.

    What to measure

    Metric What it tells you
    Time to first value Days from closed-won to the first-value milestone
    Onboarding cycle time by phase Which stage is slowing everything down
    Onboarding completion rate The share of customers finishing the plan
    Activation rate The share of users or accounts reaching the activation event
    Stalled accounts Accounts with no progress for a set period
    Early support tickets per account Whether setup friction is generating avoidable questions

    Baseline these for each track before you set targets. Published benchmarks are of limited help because definitions differ. One 2025 benchmark of 62 B2B SaaS companies, for example, reported an average activation rate around 37.5% and a time to value of about a day and a half, but those figures describe product-led signups, not enterprise implementations that take weeks. Compare yourself only with like for like.

    Early onboarding data is also your earliest health signal. Feed milestone completion, stalled status, and early support volume into your customer health score, so a customer that’s behind at day 30 shows up before the renewal conversation. Faster, smoother onboarding supports net revenue retention directly.

    A before-and-after example

    Using the illustrative 52-day example, a team makes four changes: technical discovery moves into the sales cycle, handoff fields become required, the handoff triggers automatically, and an in-app setup wizard replaces manual integration steps.

    Phase Before (days) After (days) What changed
    Handoff to CSM 6 1 Automatic trigger and required fields
    Kickoff scheduling 8 2 Scheduling link sent within a day
    Data, integration, security 21 12 Prework started in the sales cycle; setup wizard
    Configuration 7 5 Templates for common setups
    Training 5 4 Role-based in-app guides
    Waiting on stakeholders 5 3 Overdue reminders and sponsor escalation
    Total 52 27 About 48% faster

    None of the changes are exotic. They’re mostly about removing waiting. Use your own phase data to find the equivalent opportunities.

    Use the journey map to find friction

    Numbers show where time goes. Customers tell you why. Add an onboarding stage to your customer journey map, interview a handful of recent customers about what slowed them down, and compare their answers with your phase data. Common findings include unclear prerequisites, security reviews that start too late, and a champion who’s too busy to coordinate internally.

    Mistakes to avoid

    • Defining success as “kickoff held” or “configured” instead of an outcome
    • Treating every customer the same instead of assigning a track
    • Starting technical prerequisites after the contract is signed
    • Running onboarding in a private internal tool the customer can’t see
    • Letting the handoff depend on someone remembering to send a message
    • Measuring completion of tasks but not time to first value
    • Declaring victory at go-live without confirming value

    Summary

    A customer onboarding workflow takes a customer from closed-won to first value through defined stages, triggers, owners, and exit criteria. Start by defining first value as an outcome, agreed with the customer at kickoff. Then break down where the days actually go, since much of the time is usually handoff lag, scheduling, and customer-side readiness, not hands-on work.

    Segment customers into high-touch, mid-touch, and tech-touch tracks, build a six-stage workflow with automated triggers and a shared success plan, and add alerts for stalled accounts. Measure time to first value, phase cycle times, completion, and activation against your own baseline, feed early signals into your health score, and use the journey map and customer interviews to find the friction behind the numbers.

    FAQ

    What is a customer onboarding workflow?

    It’s the repeatable sequence of steps, owners, triggers, and checkpoints that moves a new customer from signed contract to first value, usually with a mix of automation and human touchpoints.

    What is time to first value?

    It’s the elapsed time from signature or closed-won to the first meaningful outcome a customer cares about, defined for each segment. It measures how quickly customers see a return on their purchase.

    How do you define first value?

    As an outcome, not an action. “Admin logged in” is an action, while “first live workflow running on real data” is an outcome. Agree it with the customer at kickoff and make it measurable.

    What is a mutual success plan?

    A shared document that lists the customer’s goals, milestones, owners, and dates, so onboarding is a jointly owned project with visible commitments on both sides.

    Should every customer get the same onboarding?

    No. Segment by complexity and size into tracks such as high-touch and tech-touch, route each customer automatically from deal data, and adjust the touch model to what each segment needs.

    Which metrics matter most?

    Time to first value, cycle time by phase, completion rate, activation rate, stalled accounts, and early support tickets per account. Baseline them by track before setting targets.

    How can we automate onboarding without losing the human touch?

    Automate the waiting, reminding, and handing off, such as triggers, task assignment, and stall alerts, and keep people for the moments that need judgment, like kickoff, security issues, and confirming value with the sponsor.

    When should onboarding start?

    Before the contract is signed. Capture technical requirements and success criteria in the sales cycle, and start security and integration prework early, so the clock doesn’t begin from zero at closed-won.

  • HubSpot Deal Stages: How to Set Up Your Sales Pipeline.

    HubSpot deal stages are the ordered steps a deal moves through inside a sales pipeline, from first conversation to closed won or closed lost. Each stage carries a win probability, which HubSpot uses to weight your pipeline and forecast, and each can require specific properties before a deal moves forward.

    Most teams inherit the default pipeline, rename a stage or two, and never look at it again. Then the forecast misses, reps argue about what “Qualified” means, and the pipeline fills with deals that haven’t moved in months. The fix usually isn’t a new tool. It’s a pipeline designed around evidence.

    This guide covers how deal stages work, how to design them, how to set probabilities from your own data, how they connect to lifecycle stages and forecast categories, and how to set it all up.

    Deal stage vs. lifecycle stage vs. forecast category

    These four fields get mixed up constantly, so it’s worth separating them before you build anything.

    Field Lives on Question it answers
    Deal stage Deals How far along is this specific deal?
    Lifecycle stage Contacts and companies What is our overall relationship with this person or company?
    Lead status Contacts and companies What is a rep doing with this lead right now?
    Forecast category Deals How confident are we that this will close this period?

    HubSpot’s default deal stages

    HubSpot’s default sales pipeline ships with seven stages and a default probability for each. The sales pipeline is available in every Sales Hub tier.

    Default stage Default probability
    Appointment Scheduled 20%
    Qualified to Buy 40%
    Presentation Scheduled 60%
    Decision Maker Bought-In 80%
    Contract Sent 90%
    Closed Won 100%
    Closed Lost 0%

    They’re a reasonable starting point, but they mostly describe what the rep has done: scheduled, presented, sent. They don’t say what the buyer has done, which is what actually predicts a close. And the percentages are generic, not yours.

    Design principles for deal stages

    • Use buyer milestones, not rep activities. “Buyer confirmed budget range” is more reliable than “demo given.”
    • Keep it to roughly five to eight stages. Too few and you lose visibility. Too many and reps skip stages.
    • Write entry and exit criteria for every stage, in one sentence each.
    • One pipeline per genuinely different motion, such as new business versus renewals. Avoid creating pipelines for every segment.
    • No graveyard stage. A “follow-up” stage where stalled deals sit forever hides risk. Close them or define a rule for moving them out.

    An example B2B SaaS pipeline

    Here’s one illustrative design. Yours should reflect your own sales process.

    Stage Entry criteria (buyer evidence) Required properties
    Discovery The buyer agreed to a first conversation about a specific problem Deal source, use case
    Qualified The buyer confirmed the problem, a rough budget, and a decision process Budget range, decision maker, timeline
    Evaluation The buyer is testing or reviewing the product with named stakeholders Champion, competitors considered
    Proposal The buyer has a written proposal and agreed to review it Amount, close date, next step date
    Negotiation Terms are being discussed, and legal or procurement is involved Procurement path, signer
    Closed Won Contract signed Contract start date, billing contact
    Closed Lost The buyer chose another option or no decision Closed-lost reason (dropdown), competitor

    For help defining the qualification evidence behind these gates, see our comparison of BANT and MEDDIC.

    Set probabilities from your own data

    HubSpot multiplies each deal’s amount by its stage probability to produce weighted pipeline. If the probabilities are guesses, so is the forecast. Replace the defaults with your actual history. Pull the closed deals from the last 12 months and, for each stage, calculate the share of deals that reached it and eventually closed won. Here’s an illustrative example in which 60 deals were won:

    Stage Deals that reached it Eventually won Win rate (use as probability)
    Discovery 400 60 15%
    Qualified 250 60 24%
    Evaluation 150 60 40%
    Proposal 100 60 60%
    Negotiation 75 60 80%

    Every won deal passed through every stage here, which is why the “won” column is constant. In real data, some deals skip stages, so adjust for that. Recalculate each quarter, and consider separate pipelines or probabilities where deal size or segment changes the odds. For more on how weighting works, see our guide to weighted pipeline.

    How deal stages connect to lifecycle stages

    Deals drive part of the lifecycle stage on the associated contact and company. In HubSpot, a record becomes an Opportunity when it’s associated with a deal, and a Customer when it has at least one closed deal, provided you’ve turned on the settings that update lifecycle stage from associations. Lifecycle stages only move forward by default, so a customer isn’t pushed back to Opportunity when a new deal is created. Decide up front which of these updates you want, and review them in your settings. Our explanation of HubSpot lifecycle stages covers the details.

    How deal stages connect to forecast categories

    Stage probability is a statistical estimate based on history. A forecast category is a person’s judgment about this deal this period. They’re different, and many teams use both. HubSpot’s forecast can use a forecast category property on deals, and some teams add their own custom category property as a confidence overlay. Check how your forecast is configured before you rely on either.

    One way to keep them consistent is to map each stage to a default category and let reps adjust only with a stated reason. Here’s an illustrative mapping:

    Stage Default category
    Discovery, Qualified Pipeline
    Evaluation, Proposal Best Case
    Negotiation Commit, if the evidence criteria are met
    Closed Won Closed
    Closed Lost Not forecasted

    Our guide to forecast categories explains how to define each label by evidence, so Commit means the same thing for every rep.

    Enforce and automate

    A pipeline is only as good as the rules behind it. HubSpot lets you require properties when a deal enters or leaves a stage, which on Professional and Enterprise plans is one of the most useful and most overlooked settings. Pair it with automation:

    • Required properties at the stages shown above, including close date and amount before Proposal, and a closed-lost reason before a deal can be marked lost.
    • Workflows on stage change: create a task for the next step, notify the account team, or alert finance when a deal reaches Closed Won.
    • Stale-deal alerts: notify the owner when a deal has sat in a stage longer than your typical time.
    • Close-date checks: flag deals whose close date has been pushed more than once. Our explanation of deal slippage covers why this matters.

    Make the closed-lost reason a dropdown, not free text, so you can report on it. It’s also the raw material for win-loss analysis.

    Reports worth building

    • Weighted pipeline by stage and by owner
    • Stage-to-stage conversion rates
    • Average days in each stage, with a list of deals beyond your normal range
    • New pipeline created against target
    • Closed lost by reason, with deal count and value

    How to set it up in HubSpot

    1. Write your stages first. Draft names, entry and exit criteria, and required properties in a document, with sales leadership signing off.
    2. Open the pipeline settings. Go to Settings, then Objects, then Deals, then Pipelines. Deal stages are managed there, not through the general Properties menu.
    3. Create or edit the pipeline. Rename stages, add new ones, and drag to reorder.
    4. Set a probability for each stage from your historical data.
    5. Set required properties for the stages that need them, if your plan supports it.
    6. Move existing deals before deleting a stage. A stage that still holds deals can’t simply be removed, so map old stages to new ones first.
    7. Brief the team, then review conversion and days-in-stage after a month and adjust.

    Mistakes to avoid

    • Keeping HubSpot’s default probabilities without checking them against your data
    • Naming stages after rep activities instead of buyer milestones
    • Creating a stage for every possible situation, so reps skip around
    • Making a closed-lost reason optional or free text
    • Letting deals sit in stages with no close date or next step
    • Building several pipelines when properties or segments would do
    • Changing stage definitions mid-quarter without telling the team

    Summary

    HubSpot deal stages track how far along each deal is, and each carries a win probability that feeds weighted pipeline. The defaults, from Appointment Scheduled at 20% to Contract Sent at 90%, describe rep activity and use generic percentages. Better pipelines use five to eight stages tied to buyer milestones, with written entry and exit criteria, required properties, and probabilities calculated from your own closed deals.

    Deal stage differs from lifecycle stage, which describes the overall relationship, and from forecast category, which captures confidence this period. Deals move contacts and companies forward through lifecycle stages when associations settings are on. Enforce the design with required properties, workflows, stale-deal alerts, and a required closed-lost reason, then review the pipeline monthly.

    FAQ

    What are the default HubSpot deal stages?

    Appointment Scheduled (20%), Qualified to Buy (40%), Presentation Scheduled (60%), Decision Maker Bought-In (80%), Contract Sent (90%), Closed Won (100%), and Closed Lost (0%). They’re editable starting points.

    How many deal stages should a pipeline have?

    Most B2B teams do well with roughly five to eight. Fewer than that limits visibility, and more than that encourages reps to skip stages or guess.

    How do I change deal stage probability in HubSpot?

    Open Settings, then Objects, then Deals, then Pipelines, edit the pipeline, and set the probability for each stage. Base the numbers on how often deals at each stage actually closed in your last 12 months.

    Is deal stage the same as lifecycle stage?

    No. Deal stage tracks one deal’s progress. Lifecycle stage describes a contact or company’s overall relationship with you. A deal being created or closed can update lifecycle stage if the related settings are on.

    Can I require fields before a deal moves to the next stage?

    Yes. HubSpot lets you set required properties at the point a deal enters a stage, available on Professional and Enterprise plans. Use it for close date, amount, next step, and closed-lost reason.

    Should I use more than one pipeline?

    Only for genuinely different sales motions, such as new business and renewals. For differences like segment or region, use deal properties and filters instead, because more pipelines make reporting harder.

    How do deal stages relate to forecast categories?

    Stage probability is a historical estimate, while a forecast category is a judgment about confidence this period. Many teams map each stage to a default category and let reps adjust with a reason. Check how your HubSpot forecast is configured.

    What should I do with deals stuck in a stage?

    Set a normal time per stage, alert the owner when a deal exceeds it, and require a next step and close date. If nothing is happening, move the deal back to an earlier stage or close it with a reason.

  • What Is Win-Loss Analysis? How to Run One

    Win-loss analysis is the practice of systematically interviewing buyers after a deal closes, whether you won, lost, or ended in no decision, to understand the real reasons behind the outcome. It compares what buyers say with what your CRM and sales team say, and turns the gaps into changes in positioning, product, pricing, and process.

    Ask a sales leader why the team lost last quarter and you’ll often hear “price” or “timing.” Ask the buyers and you’ll hear something different: a business case nobody believed, a missing integration, a champion who left, a security review that stalled. The gap between those two stories is where win-loss analysis earns its keep.

    This guide explains what win-loss analysis is, why CRM data alone isn’t enough, and how to run a simple program, with a question guide, a coding frame, and a worked example.

    What is win-loss analysis?

    Win-loss analysis means picking a set of closed deals, interviewing the people who made the decision, labeling each conversation with the same reason categories, and comparing wins with losses inside a segment. It covers three outcomes: won deals, lost deals, and no-decisions, where the buyer chose to do nothing.

    It’s not the same as a deal review, where the team talks about its own deal, or a post-mortem driven by the rep’s memory. The defining feature is the buyer’s voice, collected by someone who didn’t sell to them.

    Why CRM loss reasons aren’t enough

    Almost every CRM has a “closed lost reason” field, and most of them are unreliable in the same ways. The rep fills in the dropdown minutes after a disappointing call, often choosing the option that feels least like a mistake, and price becomes the default explanation. Independent interviews regularly find that the recorded reason and the buyer’s actual reason differ. A fair summary: reps remember losses as price, while buyers remember them as risk, timing, or a business case nobody believed.

    What the CRM says What a buyer interview might reveal
    Price The ROI wasn’t clear, so any price felt too high
    Timing The champion couldn’t get an executive sponsor
    Went with a competitor The competitor had an integration we didn’t mention
    No response Security review stalled and nobody helped them through it

    That doesn’t make CRM fields useless. They’re good for volume and rough trends, and they help you choose which deals to interview. Treat them as labels that tell you where to look, not as findings.

    What you can learn

    Finding type Example Likely owner
    Positioning and messaging Buyers don’t understand how we differ from the alternative Product marketing
    Product gaps A missing integration appears in many losses Product
    Pricing and packaging The entry plan lacks one feature buyers expect Product and finance
    Sales process We rarely reach the economic buyer Sales leadership
    Competitive One competitor wins on onboarding speed Competitive intelligence

    How to run a win-loss analysis

    1. Define the question and scope. A vague goal produces vague findings. Try something specific: “Why are we losing mid-market deals to Competitor X?” or “What makes wins in our new segment different?”
    2. Select deals deliberately. Include wins, losses, and no-decisions, across deal size, industry, and rep. Interviewing only losses teaches you what went wrong but not what’s working.
    3. Interview soon after the decision. Sources range from two to six weeks, and recall fades quickly after that. Aim for within a month.
    4. Use a neutral interviewer. The account executive who owned the deal shouldn’t run it, and neither should their manager. Buyers soften criticism when they know who they’re talking to. A product marketer, researcher, or outside firm works better. Keep the rep debrief separate, and hold it after you have the buyer data.
    5. Recruit with a clear, low-effort ask. Offer a 20 to 30 minute call, explain the feedback is confidential and used to improve, and don’t use it to win them back. Try more than one person on the buying committee.
    6. Code every interview the same way. Use a fixed set of labels so you can compare across deals.
    7. Triangulate with your data. Compare interviews with CRM stage history, cycle length, and competitors, and note where they agree and contradict.
    8. Report with sample size and confidence, then act. Run a workshop where each priority finding gets an owner and a change to a specific asset: a deck, a pricing page, a playbook, a roadmap item.

    Questions to ask buyers

    Topic Sample question
    Trigger What was going on that made you start looking?
    Alternatives What options did you consider, including doing nothing?
    Criteria What mattered most in your decision, and how did that change along the way?
    Committee Who was involved, and who had the final say?
    Experience What was it like working with our team compared with the others?
    Turning point Was there a moment when you knew where this was heading?
    Concerns What worried you most about choosing us?
    Advice If you could change one thing about how we sold to you, what would it be?

    Ask about behavior and specific moments, not opinions in the abstract. “Walk me through what happened after the demo” gets better answers than “Did you like our product?” And listen more than you talk.

    A simple coding frame

    Pick one primary reason per interview, plus an optional secondary one, from labels like these. Adapt them to your business, and keep them fixed from quarter to quarter.

    Category Meaning
    Competitive loss The buyer chose a named competitor
    No decision The buyer kept the status quo
    Product gap A needed capability or integration was missing
    Value and price Cost was hard to justify against the expected return
    Evaluation and process We didn’t reach decision-makers or support the evaluation well
    Champion and sponsor The internal advocate left or lacked influence
    Timing and priority The project was deprioritized or delayed
    Trust and risk Security, vendor stability, or implementation risk worried the buyer

    Track timing and no-decision outcomes separately from true competitive losses. A deal pushed to next quarter isn’t the same as a deal lost to a rival, and mixing them hides what’s really going on.

    A worked example

    Imagine a team interviews 24 buyers from lost and no-decision deals. In the CRM, 14 of the 24 were logged as “price.” The numbers below are illustrative.

    Primary reason from interviews Deals Action
    Value and price 4 Review packaging at the entry tier
    Business case unclear 6 Create an ROI template and train reps to use it
    Product gap (integration) 5 Publish an integrations guide; raise on the roadmap
    Champion or sponsor lost 5 Multithread earlier; require a named executive sponsor by a set stage
    Security review stalled 3 Build a security answer pack
    Other 1 None

    The CRM said price in 14 of 24 deals. Buyers named it as the main reason in four. The biggest actionable themes were an unclear business case and a missing integration, and none of them would have shown up in the dropdown. With 24 interviews, treat the percentages as directional, not precise. Say so in the report.

    Connect it to deal slippage and pipeline hygiene

    Win-loss findings are most useful when they feed your day-to-day data. Three links are worth making:

    • Standardize the closed-lost field. Replace free-form or generic reasons with the categories from your coding frame, and make the field required. Add a competitor field. Our guide to closed-loop reporting covers how those outcomes flow back to marketing.
    • Watch for slippage. Deals that keep moving to the next quarter often end as no-decisions. Interviews can reveal why, and our explanation of deal slippage shows how to catch the signs earlier.
    • Tighten pipeline hygiene. If interviews show you rarely reach the economic buyer, require that field before a deal enters Commit. Qualification frameworks like BANT and MEDDIC turn findings into required evidence.

    Each quarter, compare your CRM loss reasons with the interview findings. If they diverge, recalibrate the dropdown. Over time the CRM field gets closer to reality, and you can use it for ongoing trend tracking between interview rounds. The customer journey map is also a useful companion, since interview answers often point to specific stages where buyers got stuck.

    In-house, third-party, or AI-assisted?

    Option Advantages Watch for
    In-house (product marketing or research) Low cost, deep product knowledge Buyers may be less candid; programs fade when people get busy
    Third-party firm Neutrality and reach to lost buyers Cost, and a smaller sample of deals
    AI-moderated interviews or surveys Scale and speed Depth and nuance vary; review transcripts yourself
    Hybrid Interviews for depth, surveys for breadth More to coordinate

    Whichever you choose, the same rules apply: someone neutral asks the questions, the labels stay consistent, and each finding has an owner.

    How many interviews are enough?

    Guidance varies. Some sources suggest 15 to 20 interviews per quarter to see clear patterns, and others suggest at least 10 to 15 deals before drawing conclusions about any single pattern. A thinner round is still useful if you label it directional. Fewer than about eight interviews per cycle starts to look more like anecdotes than patterns. Start small, keep the process steady, and let the sample grow.

    Mistakes to avoid

    • Letting the account executive or their manager run the interview
    • Interviewing only losses, so you never learn what’s working
    • Waiting months, so memories fade and buyers stop responding
    • Trusting the CRM dropdown without checking it against buyers
    • Reporting percentages from a tiny sample as if they were precise
    • Producing a report without owners or follow-up
    • Using the interview to try to win the deal back

    Summary

    Win-loss analysis interviews buyers after wins, losses, and no-decisions to find the real reasons behind outcomes. It matters because CRM loss reasons are written by reps in a hurry and tend to default to price or timing, while buyers describe different drivers, such as unclear business cases, missing integrations, lost champions, and stalled security reviews.

    To run one, define a specific question, select a mix of recent deals, use a neutral interviewer, interview within about a month, code every conversation with a fixed frame, and triangulate with CRM data. Report sample size and confidence, then assign owners to each finding. Feed the results back into your closed-lost field, your qualification rules, and your deal reviews so the CRM gets closer to the truth.

    FAQ

    What is win-loss analysis?

    It’s the practice of interviewing buyers after a deal closes, whether won, lost, or ended in no decision, to learn the real reasons behind their choice and use them to improve positioning, product, pricing, and sales process.

    Why isn’t the CRM loss reason enough?

    Reps usually choose it quickly and tend to cite price or timing. Buyer interviews often reveal different reasons. Use CRM fields for volume and trends, and validate them with real buyer conversations.

    Who should conduct win-loss interviews?

    Someone neutral: a product marketer, researcher, or outside firm. The rep who owned the deal and their manager should not, because buyers soften feedback when they know who is asking.

    How soon after a deal should we interview the buyer?

    Ideally within two to six weeks. Memory fades quickly, and recruiting gets harder with time, so aim for within about a month.

    How many interviews do we need?

    Some sources suggest 15 to 20 per quarter for clear patterns. Smaller rounds are still useful if labeled directional. Keep the process consistent and grow the sample over time.

    Should we interview wins as well as losses?

    Yes. Wins show what’s working and what to protect, and they give you a baseline to compare losses against. Also include no-decision deals, which are often the largest hidden source of lost revenue.

    How do we get buyers to agree to an interview?

    Keep the ask short, offer a 20 to 30 minute call, explain that feedback is confidential and used for improvement, not for selling, and send the request from a neutral person. Try multiple contacts on the buying committee.

    What do we do with the findings?

    Hold a short workshop, rank the findings, and map each to an owner and a specific change, such as a messaging update, an ROI template, a required CRM field, or a roadmap request. Then check next quarter whether the pattern moved.

  • Salesforce to HubSpot Migration: A Practical Checklist

    Migrating from Salesforce to HubSpot comes down to three jobs: map Salesforce’s data model onto HubSpot’s, load records in an order that keeps relationships intact, and rebuild automation by hand, because it doesn’t transfer. Plan roughly six to eight weeks for a standard setup, and longer if you have custom objects, Apex code, or heavily customized flows.

    This checklist walks through the phases in order, with the checks that catch problems early. It’s written for RevOps leads and Salesforce admins who need a plan they can hand to a team.

    Before you start: four decisions

    1. Why are you moving? Cost, usability, or one platform for marketing and sales. The reason shapes what you bring across and what you leave behind.
    2. How much history comes with you? Active contacts, open deals, and recent closed deals are the usual core. Archive the rest instead of importing everything.
    3. Which HubSpot plan do you need? Custom objects require Enterprise, and workflow and reporting features vary by tier. Decide before you design.
    4. Who owns the project? One named owner, with a Salesforce admin and a sales and marketing sponsor involved.

    How Salesforce objects map to HubSpot

    Salesforce HubSpot Notes
    Account Company Import before contacts and deals
    Contact Contact HubSpot treats email as the unique identifier, so resolve duplicates first
    Lead Contact HubSpot has no Lead object; use lifecycle stage and lead status
    Person Account Contact Decide how to represent any associated company
    Opportunity Deal Rebuild pipelines in HubSpot instead of copying stages blindly
    Campaign HubSpot campaign or list Choose based on how you use campaigns
    Case Ticket Requires Service Hub
    Custom object Custom object Enterprise only; create objects and associations before importing
    Owner HubSpot user and owner Map every owner, or records arrive unassigned
    Flow, Process Builder, Apex Workflows or custom code actions Rebuilt by hand, not migrated

    Phase 1: Audit and clean in Salesforce

    Data problems compound in a new system, so fix them at the source. Run a data quality audit before you export anything.

    • Find duplicate contacts and companies, invalid emails, and records missing required fields.
    • Flag contacts with no account, since they’ll arrive in HubSpot without a company association.
    • Decide which stale leads, old deals, and unused custom fields to archive instead of migrating.
    • List every report and dashboard leadership relies on, so you can rebuild them.
    • Inventory automation, integrations, and AppExchange apps, including who depends on each.
    • Review picklist values, because HubSpot dropdowns need matching options.

    Phase 2: Design the HubSpot side first

    • Pipelines and stages. Build them in HubSpot before loading deals. Use this as a chance to simplify.
    • Properties. Create custom properties for the fields you’re keeping, with matching types and dropdown values.
    • A Salesforce ID property. Store the original Salesforce record ID on every migrated record, so you can reconcile, de-duplicate, and trace problems later.
    • Lifecycle stage and lead status. Decide how Salesforce lead statuses map. Our guide to HubSpot lifecycle stages explains the options.
    • Users, teams, and permissions. Create them before import so owners can be mapped.
    • Custom objects and associations, if you’re on Enterprise, created before any import.

    Then build a field mapping document: one row for every field you plan to migrate, with its type, format, and any picklist translation. Anything not in the document doesn’t move.

    Also decide which reporting fields to preserve, because history is hard to rebuild. At minimum, carry over the original lead source and detail, the Salesforce created date (in a custom date property), campaign history, lifecycle stage dates, owner, and closed-lost reason. Without them, your revenue attribution and funnel reports start from zero.

    Phase 3: Load in dependency order

    Importing in the wrong order breaks associations silently: the records exist, but they’re orphaned. Parents first, then children.

    Order Load Check
    1 Users and owners Every owner in Salesforce has a HubSpot match
    2 Companies Counts match; Salesforce IDs populated
    3 Contacts, with company associations Duplicate emails resolved; unassociated contacts flagged
    4 Deals: open first, then closed-won history Pipelines exist; amounts, close dates, and owners correct
    5 Tickets, if used Associated with the right contacts
    6 Activities and notes Attached to the right records

    Test the whole sequence in a sandbox or with a small batch first. A tiny rehearsal is cheaper than cleaning up a full load.

    Phase 4: Rebuild automation

    Salesforce automation does not migrate. Flows, Process Builder automations, Apex triggers, and formula fields all have to be rebuilt.

    Salesforce HubSpot approach
    Lead assignment rules Rotation and routing workflows
    Flows and Process Builder Workflows with equivalent branching
    Apex triggers Workflows with custom code actions, or an API integration
    Formula fields Calculated properties or workflow logic
    Email alerts Notifications and internal emails
    Lead scoring HubSpot score properties

    Build the workflows but keep them paused until data validation is finished, or a half-checked import will trigger emails and tasks to the wrong people. For background, see What Is a HubSpot Workflow?

    Phase 5: Validate before you go live

    • Reconcile counts for each object against Salesforce.
    • Spot-check about 5% of records by hand for each object, comparing field values and formats.
    • Check associations: every contact with a Salesforce account should have the right company, and every deal the right contact and company.
    • Verify owners, so no records are unassigned.
    • Run key reports side by side in both systems and explain any differences.
    • Test workflows with test records, then switch them on.
    • Get sign-off from sales and marketing leaders, not just the project team.

    Phase 6: Cutover and the first 30 days

    1. Agree a freeze window for Salesforce edits, or define a delta load for changes made during cutover.
    2. Load the final delta and re-run your count checks.
    3. Repoint integrations such as email, calendar, billing, and product data to HubSpot.
    4. Switch on the validated workflows and train users on the new pipeline.
    5. Keep Salesforce read-only for a defined period, so people can look things up.
    6. Review at 30 days: data quality, adoption, broken automation, and report accuracy.

    If you run both systems in parallel, HubSpot’s Salesforce connector can keep data in sync during a phased move. Decide which system owns each field and which direction it syncs, and avoid two-way writes on the same field, or the systems will overwrite each other. Hold the sync off during bulk imports.

    What doesn’t migrate cleanly

    • Automation: Flows, Process Builder, and Apex are rebuilt, not moved.
    • Formula fields and other calculated logic.
    • Files and attachments: they don’t sync through the native integration, so plan a separate approach if you need them.
    • Reports and dashboards: rebuild them in HubSpot.
    • Custom object relationships: lookups and associations need manual mapping.
    • Account hierarchies: support is limited, so check how parent-child accounts will appear.

    A realistic timeline

    Weeks Focus
    1 to 2 Decisions, audit, and cleanup
    3 to 4 HubSpot design, field mapping, sandbox rehearsal
    5 to 6 Loads and validation
    6 to 7 Automation rebuild and testing
    7 to 8 Cutover and close support

    That’s a standard CRM-only migration. Custom objects, Apex code, and AppExchange apps can push it toward 12 weeks or more. Use your own data volumes and complexity to adjust it.

    Mistakes to avoid

    • Importing contacts or deals before companies, which orphans associations
    • Copying Salesforce stages into HubSpot without redesigning the pipeline
    • Migrating every field and record instead of what’s actually used
    • Leaving owners unmapped, so automation fails
    • Activating workflows before validation
    • Skipping original source and date fields, which resets your reporting history
    • Declaring victory at go-live without a 30-day review

    Summary

    A Salesforce to HubSpot migration maps Accounts to Companies, Opportunities to Deals, and Leads to Contacts with lifecycle stage, since HubSpot has no Lead object. Clean and audit in Salesforce first, design pipelines and properties in HubSpot, build a field mapping document, and keep the Salesforce ID on every record. Load users, companies, contacts, deals, tickets, and activities in that order, because the wrong order silently breaks associations.

    Automation doesn’t migrate, so rebuild it as workflows and keep it paused until validation is done. Reconcile counts, spot-check about 5% of records, and run key reports side by side. Expect around six to eight weeks for a standard setup and longer with custom objects or code, and preserve source and date fields so your reporting survives the move.

    FAQ

    How long does a Salesforce to HubSpot migration take?

    Around six to eight weeks for a standard migration of contacts, companies, deals, and activities. Custom objects, Apex code, and heavily customized automation can push it toward 12 weeks or more.

    What happens to Salesforce Leads in HubSpot?

    HubSpot has no Lead object, so leads become contacts. Use lifecycle stage and lead status to preserve their status, and plan for duplicate emails, since HubSpot treats email as a unique identifier.

    Do Salesforce workflows and flows migrate?

    No. Flows, Process Builder automations, Apex triggers, and formula fields must be rebuilt as HubSpot workflows, custom code actions, or integrations.

    Which HubSpot plan do we need?

    It depends on what you’re bringing. Standard objects work across tiers, but custom objects require Enterprise, and workflow and reporting capabilities vary by plan. Decide the plan before you design the data model.

    Can we run Salesforce and HubSpot together during the transition?

    Yes, the Salesforce connector can keep data in sync during a phased move. Decide which system owns each field and the sync direction, and avoid two-way writes on the same field.

    What should we leave behind?

    Outdated leads, unused custom fields, old workflows, and legacy structures that no longer add value. Archive them in Salesforce or an export so nothing is lost, but don’t carry them into the new system.

    How do we keep attribution and reporting history?

    Map original lead source, created date, campaign history, lifecycle stage dates, and closed-lost reasons into HubSpot properties before you import. Reports rebuilt after the move will only be as good as the fields that came across.

  • What Is a HubSpot Lifecycle Stage? Beginner’s Guide

    A HubSpot lifecycle stage is a property on every contact and company record that shows where that person or business sits in your marketing and sales process, from first-time visitor all the way to paying customer. HubSpot ships with eight default stages, and you can customize them so your whole revenue team works from the same definition of “lead” instead of arguing about it in Slack.

    If you’ve ever had marketing call someone a “qualified lead” while sales calls the same person “just a form fill,” you already know why this property exists. It’s not a fancy feature. It’s the thing that keeps everyone honest about where a contact actually stands.

    What is a HubSpot lifecycle stage, really?

    Think of it as a label that travels with a contact or company record as they move closer to becoming a customer. It’s a default property built into every HubSpot portal, sitting on both the contact and company objects.

    HubSpot’s own documentation describes it plainly: the lifecycle stage property helps you categorize contacts and companies by where they are in your marketing and sales processes, and shows how leads are handed off between teams. That handoff piece matters more than it sounds. Most of the marketing-to-sales friction we see in RevOps (revenue operations, the function that aligns marketing, sales, and customer success processes) traces back to nobody agreeing on when a contact should move to the next stage.

    Here’s the important nuance: lifecycle stage is not the same as deal stage, and it’s not the same as lead status. Mixing these three up is one of the most common configuration mistakes new HubSpot users make.

    Lifecycle stage Deal stage Lead status
    Lives on Contacts and companies Deals Contacts and companies
    Question it answers What is our overall relationship with this person or company? How far along is this specific deal? What is a rep doing with this lead right now?
    Example values Lead, MQL, Customer Demo scheduled, Contract sent, Closed won New, Attempted to Contact, Connected
    Typically updated by Rules, workflows, and sales handoffs The deal owner The rep working the lead

    What are the default HubSpot lifecycle stages?

    HubSpot’s lifecycle stage property comes with these default stages, in sequential order:

    1. Subscriber: a contact who opted in to hear from you, usually by signing up for a blog or newsletter, but hasn’t taken any higher-intent action yet.
    2. Lead: a contact or company that converted on your website or through some other interaction beyond a subscription sign-up, like filling out a contact form.
    3. Marketing Qualified Lead (MQL): a contact or company your marketing team has qualified as ready for sales. HubSpot doesn’t decide this for you. You choose the scoring or behavior criteria that earn someone the label.
    4. Sales Qualified Lead (SQL): a contact or company your sales team has qualified as a potential customer. Its sub-stages are tracked in the separate Lead Status property.
    5. Opportunity: a contact or company associated with a deal.
    6. Customer: a contact or company with at least one closed deal.
    7. Evangelist: a customer who has advocated for your organization.
    8. Other: a catch-all for anyone who doesn’t fit the buyer journey, like a vendor or a job applicant.

    A quick, honest opinion: you probably don’t need all eight from day one. A lot of smaller B2B teams get real value from Lead, Opportunity, and Customer, and skip Subscriber, MQL, SQL, and Evangelist until their volume justifies the extra granularity. Adding stages you can’t consistently define just adds noise to your reporting.

    How does lifecycle stage automation actually work?

    By default, HubSpot’s automatic updates only move a record’s lifecycle stage forward. A form submission can’t accidentally demote a Customer back to Lead. The same applies to imports, the API, the Salesforce integration, and workflows: they can set the stage forward, but to move a record backward with those tools you first have to clear its existing value. You can still set an earlier stage manually.

    In your HubSpot settings, you can choose to set lifecycle stages automatically in three ways:

    • Set a default stage for newly created records.
    • Update the stage based on a record’s associations, for example when a deal is created and linked to a contact.
    • Set a default stage for records synced in from each connected app.

    If you turn on the association-based setting, a contact sitting at Lead moves forward to Opportunity when a deal is associated with them. A contact already marked Customer isn’t pushed back to Opportunity, because the stage only moves forward. Check your settings so you know which behaviors are on, and review the property history, which shows the source of each update.

    Pro tip: don’t rely on manual updates to keep lifecycle stages accurate. Build a workflow (an automated series of actions HubSpot runs based on triggers you set, covered in What Is a HubSpot Workflow?) that moves contacts along whenever they meet your MQL or SQL criteria. Manual updates get forgotten the moment your team gets busy, and busy is every week. Note that the “Set a property value” workflow action requires a Professional or Enterprise subscription.

    The properties HubSpot creates for you

    Every lifecycle stage, default or custom, gets its own set of calculated properties. They’re what make funnel reports possible.

    Property What it shows Useful for
    Date entered [stage] When the record entered the stage Conversion rates and cohort reports
    Date exited [stage] When it left the stage Measuring how long stages take
    Latest time in [stage] Time spent in the stage since the last entry Spotting slow handoffs (Professional or Enterprise)
    Cumulative time in [stage] Total time across every entry to the stage Records that move in and out of a stage (Professional or Enterprise)

    One practical use: build a workflow that creates a task for the contact owner when a contact’s “Date entered Sales Qualified Lead” is more than five days old and nobody has followed up. One catch from HubSpot’s documentation: records won’t enroll in a workflow based on the time-in-stage properties while they’re still in that stage. For that case, trigger on “Lifecycle stage not updated in the last X days” combined with the stage you care about.

    Write one definition per stage

    HubSpot gives you the labels. Your team has to supply the meaning. Here are illustrative definitions you might adapt. They’re examples, not recommendations for every business.

    Stage Example entry criteria Who decides
    Lead Submitted a form beyond a newsletter sign-up, with a business email Marketing
    MQL Fits your ideal customer profile and reaches an agreed engagement score Marketing, with sales sign-off on the rules
    SQL A rep has spoken with them and confirmed a real need Sales
    Opportunity Associated with an open deal Set by the deal association
    Customer At least one closed-won deal Set by the deal outcome

    For help with the qualification criteria behind MQL and SQL, see our comparison of BANT and MEDDIC.

    Why does lifecycle stage matter for a growing team?

    Without a shared definition of each stage, marketing ends up nurturing people who are actually ready to buy, and sales ends up cold-calling contacts who never asked for outreach. That mismatch wastes real budget and burns trust with prospects who get the wrong message at the wrong time.

    Lifecycle stage also becomes the backbone of your funnel reporting. Here’s an illustrative month, with made-up numbers:

    Stage Records entering Conversion from previous stage
    Lead 1,000 n/a
    MQL 150 15%
    SQL 60 40%
    Opportunity 20 33%
    Customer 8 40%

    If a stage looks off, such as more SQLs than MQLs, that’s usually a sign of a data problem (records skipping stages, imports setting stages directly, or conflicting rules), not a sign your sales team is unusually persuasive. These stage dates also feed closed-loop reporting, which connects marketing sources to revenue.

    This is also where your HubSpot tier matters. Workflow-based stage updates and time-in-stage properties require Professional or Enterprise, so it’s worth checking HubSpot Free vs. Starter vs. Professional before you build a stage model you can’t yet automate.

    Common lifecycle stage mistakes

    • Treating lifecycle stage as deal stage. They answer different questions. Keep deal progress on the deal.
    • Too many stages too soon. Every stage needs a definition and an owner, or reports get noisy.
    • Several tools setting the same stage. Imports, forms, integrations, and workflows can all write to it. Decide which one is responsible for each transition.
    • Marketing defining MQL alone. If sales doesn’t agree with the rules, they’ll ignore the label.
    • Assuming a stage can slide backward. Default tools only move it forward, so a “stuck” record may need its value cleared first.
    • Never reviewing the funnel. A report nobody opens can’t catch a broken rule.

    A simple checklist for setting up lifecycle stages

    1. List the stages you actually need. Start lean; you can add more later.
    2. Write a one-sentence definition for each stage that your marketing and sales teams both sign off on.
    3. Decide which stages update automatically and which manually.
    4. Build a workflow for MQL and SQL criteria so you’re not relying on someone remembering to update a dropdown.
    5. Set up a funnel report that shows conversion rates between each stage.
    6. Review the report monthly and fix any stage where the numbers look wrong.

    Honestly, the teams that get the most value out of lifecycle stages aren’t the ones with the fanciest setup. They’re the ones who look at the funnel report every month and argue about the weird numbers instead of ignoring them.

    Summary

    A HubSpot lifecycle stage is a property on contacts and companies that shows where each one sits between first visit and paying customer. HubSpot provides eight defaults: Subscriber, Lead, MQL, SQL, Opportunity, Customer, Evangelist, and Other. It differs from deal stage, which tracks one deal, and from lead status, which tracks a rep’s activity with a lead. HubSpot doesn’t set MQL or SQL for you, so you define the criteria.

    Automatic updates only move the stage forward, and moving a record backward through tools like workflows requires clearing its value first. Each stage gets calculated date and time properties that power funnel reports. Start with only the stages you can define, write one definition each with sales and marketing agreement, automate the MQL and SQL transitions with workflows on a plan that supports them, and review the funnel monthly.

    FAQ

    Is lifecycle stage the same as deal stage in HubSpot?

    No. Lifecycle stage tracks the overall relationship a contact has with your company, from Subscriber through Customer. Deal stage tracks progress within one specific sales deal, and a single contact can be tied to multiple deals at different stages.

    Can I customize the default lifecycle stages?

    Yes. You can rename, reorder, delete, or add stages to match your sales process, and HubSpot creates the matching calculated date and time properties for each default and custom stage.

    Does HubSpot set MQL and SQL automatically?

    No. HubSpot leaves the MQL and SQL definitions up to you, so you need to build your own scoring criteria or workflow logic to move contacts into those stages.

    What happens if a contact’s lifecycle stage seems stuck?

    Check the property history to see what last changed it. A stage set manually can sit unchanged, and because default tools only move stages forward, a record stuck at an earlier stage usually means no rule, import, or workflow ever pushed it ahead.

    Do I need to use all eight default stages?

    Not at all. Plenty of B2B teams run fine using just Lead, Opportunity, and Customer, and add Subscriber, MQL, SQL, or Evangelist later if their volume and reporting needs call for it.

    Can a lifecycle stage move backward?

    You can set an earlier stage manually. Imports, forms, the API, the Salesforce integration, and workflows only move it forward unless the existing value is cleared first. Plan for that if you need records to move back, for example when a customer churns.

    Where do I turn on automatic lifecycle stage updates?

    In your HubSpot settings for the contact or company object. You can set a default stage for new records, update stages from associations, and set a default per connected app. Review what each option does before turning it on.

  • HubSpot Custom Properties vs Default: When to Add One

    A HubSpot property is just a field on a record, like Email or Deal Amount. Default properties ship with the CRM out of the box. Custom properties are ones you build yourself. The rule of thumb: use a default property if it already captures what you need, and only create a custom one when there’s a genuine gap in what HubSpot gives you.

    If you’ve ever stared at the “Create property” button in HubSpot and wondered whether you actually need it, you’re not alone. New admins tend to swing one of two ways: they either never touch properties at all, or they go overboard and build a custom field for every little thing the sales team asks for. Neither approach ends well.

    This post breaks down the actual difference between default and custom properties, gives you a simple framework for deciding when a new one is warranted, and shows you the mess that happens when teams skip that step.

    What’s the difference between a default property and a custom property?

    A property in HubSpot is a data field attached to a record, whether that’s a contact, company, deal, or ticket. Think of a contact record like a form: Name, Email, and Phone are all separate fields, and each field is a property.

    Default properties (sometimes called standard properties) are pre-built by HubSpot and come with every account. They cover the basics: contact name, email address, phone number, company name, deal stage, and so on. The contacts object alone ships with more than 160 of these built-in fields, and companies, deals, and tickets each have their own sets on top of that.

    Custom properties are fields you create yourself to store information HubSpot doesn’t already track. Say you sell industrial equipment and need to log which certification a customer’s facility holds. There’s no default field for that, so you’d build a custom property to capture it.

    Here’s the part people miss: you can’t delete or edit a default property’s core behavior. You can edit some things, like the dropdown options on a picklist, but the underlying field itself stays put. If you want a cleaner version of an existing field (say, a dropdown instead of free text), you’re usually building a custom property alongside it, not replacing the default one.

    It’s worth being specific about what “can’t edit the core behavior” actually means in practice, since it trips people up. You can rename a default property’s label, move it to a different property group, and adjust certain field-level settings. What you can’t do is change its underlying field type (turning a free-text field into a number field, for instance) or delete it outright, even if your team never uses it. That permanence is exactly why checking before you build matters so much, a custom property you regret creating is far easier to walk back than a default one you’re stuck with forever.

    Why does the distinction actually matter?

    It matters because default and custom properties don’t play the same role in your CRM. Default fields are what most of HubSpot’s native reporting, workflows, and integrations expect to see. When you build a parallel custom field instead of using the one that’s already there, you split your data across two places and nobody’s quite sure which one is “correct.”

    That’s how property sprawl happens. It’s rarely a case of teams needing more features. Most of the time, it’s someone creating a new field before checking what already exists in the portal.

    Honestly, most of the CRM messes I’ve seen in these situations aren’t a properties problem at all, they’re a “nobody checked first” problem. A rep needed to track something, didn’t know a field for it already existed, and created a duplicate. Multiply that across a sales team for a year and you’ve got a properties list nobody trusts.

    The fix isn’t more governance software. It’s a five-minute habit: search the existing property list before you build anything new.

    Property sprawl also tends to compound in a specific, predictable way, which is worth understanding so you can spot it early. The first duplicate field rarely causes any visible problem, one rep uses it, nobody else notices. The damage shows up months later, once a report or workflow was built referencing the “wrong” one of the two fields, and now half your contacts have data in the field the report ignores. Untangling that after the fact means auditing every record, deciding which field actually holds the correct data, and migrating values, a cleanup job that’s entirely avoidable if someone had just searched the property list first.

    When should you actually create a custom property?

    Here’s a simple framework. Ask these questions in order before you hit “Create property.”

    1. Does a default property already capture this? Search the property list for the object (contact, company, deal, or ticket) first. If it’s there, use it instead of duplicating it.
    2. Is the default field the wrong format, not missing entirely? If the data exists but as free text when you need a dropdown, that’s an editing job, not necessarily a new-property job. You can often adjust the field type or the picklist options on many default properties without building a duplicate.
    3. Is this data unique to how your business operates? Things like a renewal date tied to your specific contract terms, a product tier that only your company sells, or an internal lead score your team built are all fair game for a custom property.
    4. Will this field feed a report, workflow, or segmentation you actually plan to use? If you can’t name the report or automation that will use this data, you probably don’t need the field yet.
    5. Have you checked with other teams who touch this object? A field that makes sense to sales might duplicate something marketing already tracks under a different name.

    If you get through all five and there’s still a genuine gap, go ahead and build the custom property.

    Pro tip: before creating a picklist-style custom property, check whether the default version of that field already exists with different options. Editing the existing dropdown to match your business (say, trimming HubSpot’s long default industry list down to the five or six industries you actually sell into) is usually faster and cleaner than building a parallel custom field.

    Question four deserves a bit more weight than the others, since it’s the one most often skipped in practice. It’s tempting to create a field because it feels like useful information to have on hand, even without a specific report or workflow in mind yet. The problem is that “might be useful someday” fields are exactly the ones that sit empty, half-filled, or forgotten a year later, cluttering the property list for everyone else without ever earning their keep. If you genuinely can’t name what will use the data, it’s usually fine to wait until the actual need shows up.

    What are the technical limits on custom properties?

    HubSpot caps how many custom properties you can create, and the limit depends on your subscription tier. If you’re not sure which tier your company is on or should be on, it’s worth reading through a comparison of HubSpot’s Free, Starter, and Professional tiers before you commit to a properties strategy, since the tier you’re on affects what you can build.

    Free accounts are capped at a small number of custom properties, while paid Professional and Enterprise plans allow far more per object. That ceiling exists for a reason: HubSpot wants you to actually use the fields you create, not hoard them.

    Dropdown-style (enumeration) properties also have their own internal limit on how many options a single field can hold. If you’re building a picklist with thousands of options, you’ll eventually hit that ceiling too.

    These limits matter more for growing teams than they might initially seem to. A company that starts with a handful of custom fields on a Free or Starter plan can hit its ceiling surprisingly fast once multiple teams start adding properties independently, which is yet another reason the “search before you build” habit pays off, since every unnecessary duplicate field is also quietly eating into a limited, finite budget of properties you’re allowed to create.

    A quick checklist before you create a new property

    • Searched the existing property list for this object and confirmed nothing similar exists
    • Named the specific report, workflow, or segment this new field will support
    • Picked the right field type (single-line text, dropdown, number, date, etc.) instead of defaulting to free text
    • Written a short description so other users know what the field is for
    • Confirmed with any other team that touches this object that they don’t already track this somewhere else
    • Assigned the property to a logical group instead of leaving it uncategorized

    Properties feed directly into automation, so once you’ve got your fields sorted, it’s worth understanding how a HubSpot workflow actually uses that data to trigger emails, tasks, or updates. A clean property setup is what makes those workflows reliable instead of flaky.

    Worth adding to that same checklist habit: revisit your property list periodically, not just at the moment of creating something new. A quarterly pass through each object’s property group, checking for fields that have sat empty for months or clearly duplicate another field under a slightly different name, catches the sprawl that accumulates even when everyone individually followed the checklist above in the moment.

    Summary

    Default HubSpot properties ship with every account, over 160 on the contacts object alone, and can’t be deleted or have their core field type changed, though you can edit things like dropdown options. Custom properties exist to fill genuine gaps, data unique to your business that no default field captures, but creating one before checking whether a default property already covers it is the single biggest cause of property sprawl and the “messy CRM” complaints that follow.

    The five-question framework, checking for an existing default field, confirming it’s a format problem rather than a missing field, verifying the data is genuinely unique to your business, naming the specific report or workflow that will use it, and checking with other teams first, catches most unnecessary custom properties before they’re built. HubSpot’s per-tier limits on custom properties make this habit matter even more for growing teams, since every unnecessary duplicate field eats into a finite budget shared across the whole organization.

    FAQ

    Can I delete a default HubSpot property I don’t like?

    No. Default properties can’t be deleted or fundamentally changed, though you can often edit dropdown options or move them into a different property group to reduce clutter.

    How many custom properties can I create in HubSpot?

    It depends on your plan. Free accounts have a much smaller cap than paid Professional and Enterprise accounts, which allow up to 1,000 custom properties per object.

    What happens if two teams create separate custom properties for the same data?

    You end up with duplicate, half-filled fields and reports that don’t match. This is the single biggest cause of “messy CRM” complaints, and it’s almost always solved by checking existing properties before building new ones, not by adding more fields.

    Should I use a custom property or a custom object?

    A custom property adds a new field to an existing record type like contacts or deals. A custom object creates an entirely new type of record with its own properties and pipeline logic, and it requires an Enterprise-tier subscription. Most beginner use cases only need a custom property.

    Is it ever okay to create a custom property that duplicates a default one?

    Sometimes, but only when the default field’s format genuinely doesn’t work for you and can’t be edited to fit. Even then, name the custom version clearly so your team knows which field is the one to trust.

  • HubSpot Active List vs Static List: What’s the Difference?

    A HubSpot active list automatically adds or removes contacts as they meet or stop meeting your criteria, while a static list stays frozen at whatever contacts you put in it (or matched a filter) at the moment you created it. Use active lists for ongoing segmentation and automation, and static lists for one-time snapshots like event attendee rosters.

    If you’re setting up HubSpot for the first time, lists are one of the first things you’ll bump into, and one of the first things that trips people up. You go to build a list, HubSpot asks you “Active or Static?”, and if you’ve never used the tool before, that question means nothing to you.

    Here’s the good news: once you get the concept, it’s genuinely simple. The names are actually pretty literal once you know what to look for.

    What is a HubSpot list, exactly?

    A list in HubSpot is just a group of contacts, companies, deals, or other records that share something in common. That “something” could be a job title, a form they filled out, an email they opened, or a property value like lifecycle stage (if you’re unfamiliar with that term, we cover it in our post on what a HubSpot lifecycle stage is).

    Lists exist so you can talk to the right group of people without manually digging through your whole database every time. HubSpot itself frames lists as a tool for record segmentation, filtering, and grouping to serve your business needs. Once you build one, you can use it to send an email, trigger a workflow, or just check reporting on a specific segment.

    When you create a list, HubSpot makes you choose between two types: active or static. That choice matters more than it looks like it does.

    It’s worth pausing on why HubSpot forces this choice upfront rather than letting every list just quietly work however you need. The two types aren’t really variations on the same idea, they’re built to answer two different questions: “who matches this criteria right now, continuously” versus “who was in this group at one specific moment.” Trying to answer both questions with one list type is exactly what leads to the confusion new users run into.

    What is a HubSpot active list?

    An active list (sometimes people still call it a “smart list,” an older name HubSpot used) is a list that updates itself. You set the criteria, like “contact has opened an email in the last 30 days” or “company is in the software industry,” and HubSpot keeps checking the database against those rules on an ongoing basis.

    Active lists automatically update their members based on their criteria: contacts join the list when they meet the criteria and leave when they no longer meet it. So if someone visits your pricing page today, they might get added to a “pricing page visitors” active list tonight. If they haven’t visited in 90 days, HubSpot could drop them off automatically depending on how you’ve set the filter.

    Think of an active list as a living, breathing group. It’s never really “done.” That’s exactly why it’s the backbone of most ongoing email campaigns and automation: your subscriber list for a recurring newsletter is a textbook active list use case, since it automatically manages an always-changing group of subscribers.

    A few other common active list use cases worth knowing, since they show up in nearly every HubSpot setup: a “current customers” list built on deal stage or lifecycle stage, so it automatically grows as new deals close and shrinks if a customer churns and their record gets updated; an “engaged leads” list based on recent email opens or website visits, feeding a nurture workflow that only fires for people who are genuinely still active; and a “cold leads” list catching contacts who haven’t engaged in 60 or 90 days, useful for a re-engagement campaign or for flagging records that might need cleanup.

    What is a HubSpot static list?

    A static list is the opposite. It’s a snapshot, frozen at the moment you built it. Static lists are fixed and don’t update automatically; you have to add or remove contacts by hand.

    Say you export a list of everyone who registered for a webinar last month. That’s a perfect static list. The webinar happened, the registrants are the registrants, and nothing about that group needs to change tomorrow just because someone updates their job title in your CRM.

    Static lists are best for one-time emails, infrequent campaigns, and any list that doesn’t need constant refreshing. They’re also handy for reporting purposes, since you can look back at exactly who was in a group at a specific point in time, which an active list can’t give you (the membership keeps shifting).

    Other common static list scenarios: a list of attendees from a specific conference booth you’re following up with individually, a hand-picked group of accounts your sales team wants added to a targeted ABM sequence regardless of whether they match any automated criteria, or a list of contacts flagged for a one-time data cleanup task. In each of these cases, you genuinely want the group to stay exactly as you defined it, not shift because someone’s job title changed in the CRM three weeks later.

    Active list vs static list: the core differences

    Here’s the side-by-side version:

    1. Updating: Active lists refresh automatically as records meet or stop meeting criteria. Static lists only change when someone manually adds or removes a record.
    2. Best for: Active lists suit ongoing campaigns, workflows, and behavior-based targeting. Static lists suit one-time sends, event rosters, and point-in-time reporting.
    3. Editing after creation: You can add or remove filters on an active list at any time and it’ll reprocess. A static list’s membership is fixed once processed; you add or remove records one by one instead of changing filters.
    4. Use in automation: Active lists pair naturally with a HubSpot workflow because the enrollment criteria keeps working in the background. Static lists can still trigger workflows, but the group won’t grow or shrink on its own afterward.

    Honestly, most of the confusion we see with new HubSpot users isn’t about which list type is “better.” It’s that they default to static lists out of habit (because it feels safer and more controlled) when an active list would save them hours of manual list maintenance every month.

    That instinct toward static lists is understandable, since a frozen group feels predictable in a way a list that changes on its own doesn’t. In practice, the opposite is usually true: an active list you’ve configured correctly requires zero ongoing attention, while a static list you’re trying to use for ongoing segmentation requires someone to remember to update it every single time, which is exactly the kind of manual task that quietly stops happening after the first few weeks.

    Can you convert one list type to another?

    Yes, and this used to be a real pain point. HubSpot rolled out an update that lets you convert a static list to an active list (and vice versa) without losing the list ID or breaking references to it in workflows and emails. Before that, converting meant cloning the list and starting over, which broke every automation pointing at the old list.

    To convert, open the list, go to the Actions menu in the top right, and select the convert option. One catch: only static lists that were originally created with filters are eligible to convert to active, since HubSpot needs those filters to know what criteria to apply going forward.

    Pro tip: if you’re not sure which type to pick when you’re building a new list, lean active by default. It’s easier to freeze an active list’s membership later than to retroactively add dynamic rules to something you built as static.

    How to create a list in HubSpot (quick steps)

    1. Navigate to Contacts (or Companies, Deals, Tickets) and click Lists.
    2. Click Create list in the upper right.
    3. Choose the record type your list is based on.
    4. Choose Active list or Static list from the dropdown.
    5. Set your filter criteria in the left panel and click Apply filter.
    6. Name the list clearly (something like “Active – Pricing Page Visitors – Last 7 Days” beats a vague name every time).
    7. Save and let HubSpot process the list.

    That’s really the whole workflow. The hard part isn’t the clicking, it’s deciding what criteria actually reflect the audience you’re trying to reach.

    A naming convention worth adopting from day one, especially once you have more than a handful of lists: prefix every list name with its type (“Active – ” or “Static – “) the way the example above does. Six months into using HubSpot, a growing team can easily accumulate fifty or more lists, and a consistent naming pattern is the difference between finding the right one in seconds versus opening five lists to figure out which is which.

    Summary

    Active lists in HubSpot update themselves continuously based on filter criteria, contacts join and leave automatically as their properties or behavior change, which makes them the right choice for ongoing campaigns, workflows, and anything behavior-based like a newsletter or a nurture sequence. Static lists freeze at the moment of creation and only change through manual editing, which fits one-time sends, event rosters, and point-in-time reporting where you specifically want the group to stay fixed.

    The most common mistake new users make is defaulting to static lists out of habit because a frozen group feels safer, when an active list built correctly requires far less ongoing maintenance. HubSpot allows converting between the two types without breaking existing workflow or email references, so when in doubt, lean active by default, since it’s easier to freeze an active list’s membership later than to retroactively add dynamic filtering to something built as static.

    FAQ

    Is a HubSpot smart list the same as an active list?

    Yes. “Smart list” was HubSpot’s older name for what’s now called an active list. If you see the term in an old blog post or a coworker’s notes, it’s referring to the same dynamic, self-updating list type.

    Which list type should I use for a newsletter?

    Use an active list. A recurring newsletter needs a subscriber group that keeps updating as people opt in or unsubscribe, and that’s exactly what active lists are built for.

    Can I manually add contacts to an active list?

    Not directly the way you can with a static list. Active list membership is controlled entirely by the filter criteria you set, so if you want someone included, you generally need to adjust their properties or the list’s filters rather than adding them one by one.

    Do static lists update at all?

    Only if you update them yourself. A static list’s membership stays exactly as it was when you last added or removed a contact, it will not react on its own to new form fills, property changes, or behavior.

    Why does HubSpot even offer two list types instead of one?

    Because they solve different problems. You want dynamic, always-current segments for ongoing marketing and automation, but you also want frozen, reliable snapshots for reporting or documenting who was part of a specific one-time group. Trying to force one list type to do both jobs usually ends in messy data.