Tag: CRM setup

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

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