Tag: lifecycle stage

  • What Is a Sales and Marketing SLA?

    A sales and marketing SLA (service-level agreement) is a written, two-way agreement between marketing and sales that defines what each team commits to at the lead handoff. Marketing commits to delivering leads that meet agreed quality and volume standards, and sales commits to following up within a set time, making a minimum number of attempts, and reporting back on what happened.

    If marketing says the leads are great and sales says nobody is qualified, you probably don’t have a leads problem. You have an agreement problem. Nobody wrote down what “qualified” means, how fast a rep should respond, or what happens to a lead that sales declines. An SLA turns those unspoken assumptions into rules both teams can measure.

    This guide explains what an SLA covers, offers a copyable template, and shows how to enforce it in HubSpot.

    What is a sales and marketing SLA?

    It’s an operating agreement, not a legal contract. The best ones are bidirectional. Marketing commits to quality and quantity, and sales commits to speed, follow-up, and feedback. Each commitment has a number, an owner, and a way to measure it, so a missed commitment shows up in a report instead of a argument.

    It’s also not a one-time document. Definitions and targets change as your product, market, and team change, so the SLA needs a review rhythm of its own.

    Why it matters: the cost of slow follow-up

    Speed is the most widely cited reason. A 2011 Harvard Business Review study of online sales leads, “The Short Life of Online Sales Leads,” found that firms that tried to contact a lead within an hour were nearly seven times as likely to qualify it as firms that waited even an hour longer, and over 60 times as likely as firms that waited a day or more. It also found an average response time of about 42 hours among companies that responded at all. The study is more than a decade old and covers online leads specifically, so don’t treat the multiples as a forecast for your business. The direction, though, matches what most revenue teams see: interest fades quickly.

    An SLA also stops leads from falling into a “black hole,” where marketing hands them over, sales never works or rejects them with no reason, and nobody learns anything. It connects directly to your lifecycle stage definitions, because the handoff happens at a stage change.

    What an SLA should cover

    Component The question it answers Example commitment
    Definitions What counts as an MQL, sales-accepted lead (SAL), and SQL? One written definition each, with required data
    Handoff and routing Who gets the lead, and how? Assigned within five minutes by territory rules
    Response time How fast does sales make first contact? Within one hour for demo requests
    Follow-up attempts How many tries, across which channels? At least three attempts over five business days
    Disposition and feedback What happens to every lead? Accepted, rejected, or recycled with a reason within ten business days
    Volume and quality What does marketing deliver? A target number of MQLs that meet the definition
    Reporting and governance How do we know, and who reviews it? A weekly compliance report and a monthly review

    Start with definitions, response time, follow-up attempts, and standard disposition reasons. You can add volume targets and finer detail once those are working.

    Tier response times by lead type

    A single response time for every lead is too blunt. A demo request signals far more intent than an ebook download. Here’s an illustrative tiering. The times are examples to adapt, not benchmarks.

    Lead type First touch Follow-up attempts Disposition due Escalation if missed
    Demo or pricing request Within 1 hour 4 over 5 business days 5 business days Notify the manager after 2 hours
    High-intent inquiry or trial signup Within 4 hours 3 over 5 business days 7 business days Notify the manager after 8 hours
    Content download or webinar attendee (MQL) Within 1 business day 3 over 10 business days 10 business days Reassign after 2 business days

    Define when the clock starts. It should start when the lead is created or reaches the MQL stage, not when a rep first looks at it. And decide how after-hours and holidays work, since a one-hour SLA means little at 2 a.m.

    A sales and marketing SLA template

    Copy this into a shared document and replace the bracketed values with your own.

    Section Template language
    1. Purpose This agreement defines how marketing and sales work together to turn leads into pipeline and revenue, and how we hold each other accountable.
    2. Definitions MQL: a contact who meets [fit criteria] and [engagement score or behavior]. SAL: an MQL that sales has reviewed and agreed to work. SQL: a SAL where [qualification criteria, such as budget, need, and timeline] are confirmed. Required data on every MQL: [company, title, email, source, lead score].
    3. Marketing commits to Delivering [X] MQLs per [month or quarter] that meet the definitions above. Passing complete data and a short context note (source, last action, interest). Reviewing rejected-lead feedback monthly and adjusting targeting.
    4. Sales commits to First contact within [time] for [lead type]. At least [number] attempts across [channels] over [days]. Updating the lead status after every attempt. Marking each lead accepted, rejected, or recycled, with a reason code, within [days].
    5. Routing Leads are assigned by [territory, round robin, or account owner]. Unassigned leads are reassigned after [time] to [fallback owner].
    6. Disposition codes Accepted. Rejected: [wrong fit, wrong contact, no budget, duplicate, other]. Recycled: [not ready, no response, future timing]. A reason is required for every rejection and recycle.
    7. Recycle rules Recycled leads return to marketing nurture and may re-enter as MQLs after [days or new activity].
    8. Escalation If a response or disposition deadline is missed, the lead owner’s manager is notified at [time]. Repeated misses are reviewed in the monthly meeting.
    9. Reporting RevOps publishes weekly: median time to first touch, SLA compliance rate, attempts per lead, acceptance rate, and rejection reasons.
    10. Review Sales, marketing, and RevOps leaders review monthly. Definitions and targets are revisited each quarter or when the ideal customer profile changes.
    11. Sign-off [Head of Sales], [Head of Marketing], [RevOps lead], dated and versioned.

    The definitions section depends on how your team scores and qualifies. See our guides to building a lead scoring model sales trusts and to BANT and MEDDIC for the criteria behind MQL and SQL.

    Enforcing the SLA in HubSpot

    An SLA that lives only in a document gets ignored. Build the commitments into the system:

    • Lifecycle stages and timestamps. HubSpot records the date a contact enters each lifecycle stage, so “time from MQL to first touch” is measurable.
    • Lead routing. Use workflows to assign an owner when a contact becomes an MQL, and create a task with a due date that matches the SLA. For tool options, see our guide to AI tools for routing, handoffs, and pipeline hygiene.
    • Lead status as disposition. Use lead status values, such as attempted to contact, connected, and unqualified, with a required reason for rejections.
    • Breach alerts. Build a workflow that notifies the owner’s manager when a lead sits with no logged activity past the deadline.
    • Reports. Create views for time to first touch, SLA compliance by rep and by lead type, acceptance rate, and rejection reasons.

    Some of these features, such as workflow actions that set properties, depend on your HubSpot plan, so check what yours includes. See also What Is a HubSpot Workflow?

    Metrics to track

    Metric What it shows Owner
    Median time to first touch Whether sales is meeting the speed commitment Sales
    SLA compliance rate The share of leads handled within the deadlines Sales and RevOps
    Attempts per lead Whether follow-up is real or a single call Sales
    Acceptance and rejection rates Whether the MQL definition matches what sales wants Marketing and sales
    Rejection reasons Where targeting or data is going wrong Marketing
    MQL-to-SQL conversion The end-to-end quality of the handoff Both

    Baseline these for a month before you set targets. If median first touch is 19 hours today, a one-hour target for every lead is a fantasy. A staged target, such as one hour for demo requests first, is more realistic. Outcomes feed back to marketing through closed-loop reporting.

    Extend the SLA past the handoff

    Many teams stop at the lead handoff, but the same logic helps later. Sales can commit to pipeline hygiene standards: a next step and close date on every open deal, stage updates within a set time, and a closed-lost reason on every loss. That keeps the forecast and marketing’s attribution reliable. Our guide to deal slippage shows what happens when those fields go stale.

    Mistakes to avoid

    • Writing an SLA that only binds sales, so marketing has no accountability for quality
    • Setting one response time for every lead type
    • Not defining when the clock starts, or what happens after hours
    • Letting reps reject leads without a reason code
    • Using the SLA to assign blame instead of to find and fix gaps
    • Skipping enforcement in the CRM, so the agreement lives in a document
    • Never reviewing the SLA after it’s signed

    Summary

    A sales and marketing SLA is a two-way agreement defining what marketing delivers, such as leads that meet agreed quality and volume standards, and what sales commits to, such as response times, follow-up attempts, and reasons for every rejection. It matters because slow follow-up costs conversions, and because shared definitions end the argument over lead quality. A well-known HBR study of online leads found that responding within an hour made firms nearly seven times as likely to qualify a lead as waiting one more hour, though the study is old and specific to online leads.

    Cover definitions, routing, response time, follow-up attempts, disposition and feedback, volume and quality, and reporting. Tier response times by lead type, define when the clock starts, and baseline before setting targets. Enforce the SLA with lifecycle stage timestamps, routing workflows, required reason codes, breach alerts, and compliance reports, and review it monthly.

    FAQ

    What is a sales and marketing SLA?

    It’s a written agreement between the two teams setting out what marketing commits to deliver and what sales commits to do with each lead, including response times, follow-up attempts, and feedback, with metrics for both.

    What should sales commit to in an SLA?

    A maximum time to first contact, a minimum number of follow-up attempts across channels, and a deadline to accept, reject, or recycle each lead with a standard reason code.

    What should marketing commit to?

    A volume of MQLs that meet the written definition, complete data and context on each lead, and a monthly review of rejected-lead feedback to improve targeting.

    How fast should sales respond to a lead?

    It depends on lead type and your baseline. High-intent requests such as demos often warrant minutes to an hour, while content downloads can allow a business day. Set tiers from your own data and tighten them over time.

    What’s the difference between an MQL, SAL, and SQL?

    An MQL meets marketing’s fit and engagement criteria. A SAL is an MQL that sales has reviewed and agreed to work. An SQL is a lead where sales has confirmed qualification criteria such as need, budget, and timing.

    Who owns the SLA?

    Sales and marketing leaders own the commitments, and RevOps typically owns the measurement, workflows, and reporting that make them enforceable.

    What happens if the SLA is missed?

    Define it upfront: automatic alerts to the manager, reassignment after a set time, and a standing agenda item in the monthly review. The goal is to find the cause, such as capacity, routing, or lead quality, not to assign blame.

    How often should we update the SLA?

    Review performance monthly and revisit definitions and targets quarterly, or whenever your ideal customer profile, product, or team structure changes.

  • 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.

  • 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 Closed-Loop Reporting? A RevOps Beginner’s Guide

    Closed-loop reporting is the practice of connecting your marketing data (where a lead came from) to your sales data (whether that lead turned into revenue), so both teams can see which campaigns actually produce paying customers, not just form fills. It closes the gap between “we got a lead” and “we got paid,” giving RevOps teams a single, trustworthy view of what’s driving growth.

    If you’ve ever sat in a meeting where marketing swears a campaign is crushing it while sales says the leads are garbage, you’ve felt the problem closed-loop reporting solves. Both teams are usually right, from their own narrow view. The disconnect happens because their data never talks to each other.

    What Is Closed-Loop Reporting, Exactly?

    At its core, closed-loop reporting connects marketing activity (campaigns, channels, content) to what happens after sales gets involved: qualified or not, won or lost, revenue or no revenue. The “loop” closes when outcome data from your CRM (customer relationship management system, the database where you track deals and customers) flows back to whoever owns marketing data, so they can see the downstream result of their work.

    A simple way to think about it: closed-loop reporting traces a contact from the original marketing source and campaign, through qualification, to the deal that was eventually won or lost. Without that trace, you’re left guessing which channels are worth the budget.

    How Does Closed-Loop Reporting Work?

    The mechanics are less complicated than the name suggests. Here’s the basic flow:

    1. A visitor arrives through some channel (organic search, a paid ad, a referral), and that source gets tagged.
    2. They convert into a lead, usually by filling out a form or booking a demo.
    3. The lead gets handed to sales and becomes a deal or opportunity inside the CRM.
    4. The deal closes, won or lost, and that outcome gets recorded.
    5. The outcome data flows back to the marketing side, showing which original source and campaign produced the win (or the loss).

    That last step is the one most companies skip. Plenty of teams nail steps one through four and never close the loop back to marketing, which means marketing keeps optimizing for lead volume instead of revenue.

    Open-Loop vs. Closed-Loop Reporting: What’s the Difference?

    Open-loop reporting stops at the handoff. Marketing tracks leads generated, sales tracks deals closed, and nobody connects the two. Closed-loop reporting goes one step further and ties marketing activity all the way through to the sales outcome, so you can see which campaigns, channels, and offers generate actual customers and revenue, not just leads or traffic.

    Honestly, most companies think they’re doing closed-loop reporting when they’re really doing open-loop reporting with extra dashboards. If your marketing reports stop at “MQLs generated” (marketing qualified leads, meaning leads marketing has flagged as sales-ready) and never mention revenue, you haven’t closed anything.

    What the Difference Looks Like in Numbers

    Here’s a made-up quarter for three channels. The figures are illustrative, not benchmarks.

    Channel Spend Leads Cost per lead Won deals Cost per won deal
    Paid social $20,000 400 $50 2 $10,000
    Webinars $12,000 120 $100 6 $2,000
    Organic search $8,000 200 $40 8 $1,000

    An open-loop report would rank these on cost per lead, and paid social looks respectable at $50. The closed-loop column tells a different story: paid social is the most expensive way to get a customer, at five times the cost of webinars, even though webinars produce the most expensive leads. Open-loop shows you leads. Closed-loop shows you customers.

    The Data You Need to Capture

    You don’t need a dozen systems. You need a handful of fields captured consistently and kept intact from first touch to closed deal.

    Field What it holds Why it matters
    Original source and campaign How the contact first arrived The anchor for the whole trace
    Lifecycle stage and date stamps When the contact became a lead, MQL, SQL, and customer Lets you measure speed and drop-off between stages
    Contact-to-deal association Which contacts belong to which opportunity Without it, revenue can’t be tied back to a source
    Deal amount and close date The value and timing of the outcome Turns leads into revenue
    Closed-lost reason Why a deal didn’t close Shows lead quality problems by source
    Account or company ID The company behind the contacts Handles B2B deals with several contacts

    If you’re unsure how lifecycle stages should be defined, see our explanation of what a HubSpot lifecycle stage is. Clear stage definitions are what make the date stamps meaningful.

    Where the Loop Usually Breaks

    What breaks What you’ll see The fix
    Source gets overwritten Every contact shows “direct” or the latest form they filled in Lock the original source and record later touches separately
    Inconsistent campaign naming One campaign appears under five different names Agree a naming convention and use dropdowns, not free text
    Contacts not linked to deals Revenue by source is blank or tiny Require at least one contact on every deal
    Duplicate records One buyer counted as three leads Dedupe on a schedule, matching on email and domain
    Offline touches missing Events and phone calls get no credit Log them as campaigns or activities in the CRM

    B2B Wrinkles: Long Cycles and Many Contacts

    Two things make B2B closed-loop reporting trickier than it looks. First, sales cycles are long. A lead created in January may not close until summer, so a report grouped by close date mixes leads from many different months and campaigns. Group by lead creation month instead (a cohort view), and check each cohort again as its deals resolve.

    Second, deals involve buying committees. Several people at the same company may touch your content, and only one of them fills out the form that creates the deal. Associate every involved contact with the deal and report at the account level, or you’ll credit a single contact and miss the rest of the influence. Attribution models (first touch, last touch, or multi-touch) are a separate choice layered on top. None of them works if the underlying records aren’t connected, so fix the connections before debating the model.

    Why Does Closed-Loop Reporting Matter?

    It matters because much of the B2B buying process happens before a salesperson ever gets involved. A widely cited Gartner study found that B2B buyers spend only about 17% of their total purchase journey meeting with potential suppliers. The rest happens across content, research, and internal discussion that marketing influences and sales rarely sees recorded against a deal.

    That’s a lot of invisible influence. If you can’t connect that activity back to a closed deal, you’re flying blind on where your best customers actually come from.

    There’s also a real cost to staying disconnected. Research on sales and marketing alignment has consistently linked tight alignment with better win rates and customer retention than teams that operate in silos. Closed-loop reporting is one of the most practical ways to build that alignment, because it forces both teams to agree on what success means: revenue, not just activity.

    If you’re still figuring out whether your company needs someone dedicated to building this kind of connected reporting, read 5 Signs Your Company Needs a Dedicated RevOps Hire. Closed-loop reporting is usually one of the first things to fall apart without a RevOps owner, because nobody else has the job of making marketing and sales data agree. It also feeds directly into forecasting, since a pipeline you can trace back to its source is easier to trust. Our guide to sales pipeline vs. sales funnel covers how those two views fit together.

    A Practical Checklist to Start Closing the Loop

    You don’t need a six-month project to get started. Here’s a realistic first pass:

    • Pick one system of record. Decide whether your CRM or your marketing platform owns the source of truth for lead source data.
    • Standardize your source and campaign tagging. If every rep and every campaign names things differently, nothing will match up later.
    • Map your lead-to-deal journey. Document every stage a contact moves through, from first touch to closed-won or closed-lost.
    • Require a reason on every lost deal. A “closed lost reason” field, filled in consistently, tells you more about lead quality than almost any other data point.
    • Build one shared report. Not a marketing report and a separate sales report. One view both teams look at.
    • Review it together, monthly. Reporting without a recurring conversation just becomes another dashboard nobody opens.

    Pro tip: start the loop with your lost deals, not your won ones. Everyone wants to study why a deal closed, but the lost-deal data is usually where you find the campaign or lead source that’s quietly wasting your budget.

    If you’re newer to this whole space, back up a step and get the full picture of what RevOps covers. Our guide on what RevOps is and how it works is a good place to start before digging into any one piece of it, like reporting. And to see how mature your reporting is today, the RevOps maturity framework offers a simple way to assess it.

    Summary

    Closed-loop reporting connects marketing data (where a lead came from) with sales outcomes (whether it became revenue), so teams can see which channels and campaigns produce customers instead of just leads. It works by tagging the original source, carrying it through the CRM to the won or lost deal, and flowing the outcome back to marketing. Open-loop reporting stops at the handoff, which is how a channel can look cheap on cost per lead and turn out to be the most expensive way to win a customer.

    To get started, capture a small set of fields consistently: original source and campaign, lifecycle stage dates, contact-to-deal associations, deal value, closed-lost reasons, and an account ID. Watch for common breaks, such as overwritten sources and inconsistent naming. For B2B, use cohort views for long cycles and report at the account level for buying committees. Then build one shared report and review it together every month.

    FAQ

    Is closed-loop reporting the same as attribution?

    Not quite, though they’re related. Attribution is about assigning credit to specific touchpoints. Closed-loop reporting is the broader system that makes attribution possible, by connecting the data sources attribution depends on.

    Do I need a specific tool to do closed-loop reporting?

    You need a reliable integration between your marketing automation platform and your CRM, consistent campaign and source tagging, and clean mapping of leads to opportunities. Plenty of CRMs, including HubSpot and Salesforce, support this natively or through integrations.

    What’s the single biggest blocker to closing the loop?

    Inconsistent tagging. If sales reps and marketers aren’t using the same naming conventions for sources and campaigns, your data will never line up cleanly, no matter how good your tools are.

    Can small companies benefit from closed-loop reporting, or is it just for enterprise teams?

    Small teams often benefit more. You have less budget to waste, so knowing which channels produce paying customers, not just leads, matters even more when every dollar counts.

    How often should we review closed-loop data?

    Monthly is a reasonable baseline for most B2B teams, though fast-growing companies with high lead volume may want a biweekly check-in instead.

    How long before closed-loop data becomes useful?

    It depends on your sales cycle. With a 60-day cycle you can learn a lot within a quarter. With a six-month cycle, early reports will show leads and pipeline, and revenue by source will only fill in as each cohort’s deals close, so lean on stage conversion rates in the meantime.

  • 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.