100 Questions Every HubSpot Build-Out Runs Into

A list is a saved, reusable group of contacts, companies, or other records that match criteria you define — like industry, location, lifecycle stage, or engagement history. Once saved, you can use that same group again and again: to send an email, enroll people in a workflow, or build a report. A filtered view, on the other hand, is usually a temporary way of looking at your data on a page — it doesn’t create a named, reusable group. If you catch yourself filtering the same way more than once, that’s usually a sign it should become a list instead.

A static list is a fixed snapshot — records stay on it until someone manually removes them, even if their details change later. An active list continuously re-checks its criteria and automatically adds or drops records as their data changes (for example, when someone unsubscribes or a property updates). Active lists are ideal for “always current” groups, like current customers. Static lists are better when you need a locked group that won’t shift while you’re working with it, such as a one-time campaign mailing list. You can convert a list from one type to the other if your needs change.

There are two main ways. From an open record (or a set of selected records in a table), you can use the actions menu to add them directly to an existing static list. Alternatively, when building or editing a list, you can define filter criteria and the system will automatically pull in everyone who matches. Active lists only support the criteria-based method, since their membership is rule-driven; static lists support both manual and criteria-based additions.

From most list views, tables, or report drill-downs, you can use the Export option to download the records as an Excel or CSV file, choosing which columns/properties to include. For larger exports, you’ll typically get an email notification when the file is ready. If a field you need is missing from your export, check that it’s added as a column in the view first — exports generally only pull what’s visible on screen.

By default, HubSpot only strictly requires an email address to create a contact record. Many teams choose to also require fields like name or company as part of their own process, but that’s a configuration decision your team makes — not a built-in HubSpot rule. If a required field is creating friction somewhere (like quick manual entry), it can be adjusted.

Either approach works — start with whichever record you’re more certain about. If you don’t yet know the right point of contact, it’s often cleanest to create the company first and add the contact once you know who that is. If you already know the person, creating the record from the contact page will typically auto-associate them with their company (matched by company name or email domain), saving you a step.

Yes. A company record automatically rolls up all activity logged on its associated contacts — calls, meetings, notes, and tasks all appear in the company’s timeline as well. That’s why it’s generally best practice to log activity at the contact level even when you’re thinking about the relationship primarily at the company level; nothing gets lost.

The “owner” field identifies who on your team is responsible for a given record, and it drives personalized views, task/notification routing, and reporting. By default, HubSpot does not assign an owner automatically — a record stays unowned until someone sets it manually or you build a rule/workflow to assign it based on criteria like territory, lead source, or company size. Contact owner and company owner are separate fields and won’t automatically match unless you set up a process to keep them aligned.

Any list, table, or dashboard can be filtered by an owner field (contact owner, company owner, deal owner, etc.) and set to filter for the current user — so it only shows records owned by whoever is logged in. Many teams set this as the default filter on frequently used pages so each person automatically sees just their own records without re-filtering every time.

If you’re adjusting your own personal view (or the unmodified default view), the change is visible only to you — no one else’s view is affected. To give the whole team a shared view, you need to explicitly save your filtered/customized version as a new, named view (and share or clone it out to others) rather than just tweaking your own settings. That way everyone can keep a personal version without disturbing the official shared one.

Your historical data doesn’t have to be lost. We typically export what’s in the old system and import it into HubSpot in stages — usually companies/accounts first, then contacts, then historical activity like notes, deals, and past communications. For larger or older data sets, this is done in batches with checks along the way to confirm records map correctly. Some legacy platforms limit how far back you can export, so we work with whatever is available and flag any gaps rather than losing that context.

A spreadsheet with clean, consistent column headers is the key — ideally a single sheet/tab per import. At minimum you need some kind of unique identifier (an account or customer number works well) plus the core fields you want to bring over. The cleaner and more consistent the data (correct spelling, one value per column), the more accurately it maps into HubSpot fields. We always confirm the field mapping with you before anything actually imports.

Duplicates usually happen when an import doesn’t match against something that’s already in HubSpot — without a shared unique identifier, HubSpot creates a brand-new record instead of updating the existing one. The fix is a repeatable process: export what’s already there, match new data against existing identifiers (like Record IDs or account numbers), and only then import. That’s why we build a defined import process rather than just dropping a new file in each time.

Every contact, company, deal, or other record gets a unique Record ID automatically the moment it’s created in HubSpot — you don’t assign it yourself. It’s the most reliable way to match records during an import or an ongoing data sync, since names and emails can be entered inconsistently but the Record ID never changes. Wherever possible, we build imports and integrations around Record ID matching so repeat updates don’t create new duplicates.

Nothing gets deleted outright. Merging combines the two records — the surviving record keeps its own data and picks up anything from the other record that it didn’t already have, including notes, emails, deals, and other activity history. You choose (or HubSpot suggests) which record stays as the primary, and any subscriptions or associations carry over rather than disappearing.

HubSpot has a built-in duplicate management tool that flags likely matches — based on things like name, email, or domain — for you to review and merge, and bulk merging is available on certain plans. It won’t catch everything automatically, though; duplicates with different email addresses or slightly different company names often need a manual review or a specialized dedupe tool. A common approach is letting HubSpot handle the obvious matches and running a periodic manual or third-party pass for the rest.

It depends on what’s in your import file. If your spreadsheet includes something that ties a contact to its company — a shared account number or domain, for example — that association gets created automatically during import. If that link is missing, contacts can land in HubSpot without any company attached, which is why we recommend always including a company-matching column in your import file.

Generally, no — especially if those contacts came in through an ongoing integration or sync. Many data sources will simply re-import that same person later with none of the history that explains why they went inactive. A safer approach is to flag inactive records (with a status field or lifecycle stage) so they’re excluded from marketing and reporting, while keeping the record itself intact.

Yes, within a limited window. HubSpot keeps deleted records recoverable for a set restore period (typically around 90 days) before they’re permanently removed. Before any large cleanup or bulk-delete effort, it’s also good practice to take a backup export first as an extra safety net.

This is usually handled with a parent/child company structure — one parent company record for the overall account, with a separate child company record for each location, all linked together. That way each location can carry its own contacts and activity while still rolling up to the parent account for reporting.

Yes. HubSpot supports multi-object imports, where different sections of your file map to different record types (companies, contacts, deals, etc.), and you can specify which records should be associated with each other as part of that same import. This avoids importing everything separately and manually linking records afterward.

Lifecycle stage tracks where a contact or company sits in your overall relationship with you (subscriber, lead, marketing qualified lead, opportunity, customer, etc.). Deal stage tracks the progress of one specific sales opportunity through your pipeline (e.g., discovery, proposal, negotiation, closed-won/closed-lost). They answer different questions — lifecycle stage is “how do we relate to this person or company,” deal stage is “how far along is this particular deal” — so they aren’t interchangeable. Pipeline and revenue reporting should be built from deal stage/deal data, not lifecycle stage, since lifecycle stage isn’t designed to reflect the status of an individual opportunity.

This typically happens when contacts were imported or synced from another system without a company association included, or when the data HubSpot needs to match on (like a domain or account number) didn’t line up. HubSpot can auto-associate contacts to companies by matching email domain, but custom identifiers usually need a one-time cleanup or an ongoing workflow to bridge the gap. Going forward, creating new contacts and deals from the correct company record — rather than as standalone entries — helps the association carry through automatically.

Deal owner is a property on the deal record. It’s usually set automatically when the deal is created, but it can be reassigned manually or automatically through a workflow (for example, changing the deal owner the moment a deal is marked closed-won). If you need to track other people who contributed to a deal without changing who owns it, a separate multi-user field can be added so ownership and contribution credit stay independent of each other.

The close date updates automatically the instant a deal is moved into a closed-won or closed-lost stage — it captures the date of that click, not a date you choose ahead of time. If a deal is actually closed later than when it gets marked in HubSpot, the close date field can be edited manually afterward so forecasting and historical reporting stay accurate.

At minimum, a closed-lost reason should be captured so you can analyze trends later. Extra context, such as competitor details, is helpful but generally optional — a deal shouldn’t be blocked from closing just because a “nice-to-have” field is left blank.

The forecast tool pulls deals based on amount, close date, deal owner/team, and stage — so a deal can appear “missing” simply because the forecast view is filtered to the wrong date range, or because the viewing team doesn’t have the right members assigned to it. Before assuming data is missing, check the date filter and confirm the correct owners or team roster are included in that forecast view.

Yes — HubSpot supports multiple deal pipelines, each with its own set of stages. It’s common to use separate pipelines for genuinely different processes, such as a sales pipeline versus a service/project pipeline, or different pipelines for different product lines or business units. As a rule of thumb: if the steps and the team running them are meaningfully different, a separate pipeline usually makes more sense than adding extra stages to a shared one; if the process is basically the same, keeping it in a single pipeline tends to make reporting cleaner.

Yes. Renaming a stage is safe at any time — it’s just a label change, and deals sitting in that stage aren’t affected. Removing a stage takes a bit more care, since any deals currently in it need to be moved to another stage first. It’s worth checking how many deals occupy a stage before deleting it, and confirming that no workflows or reports reference that stage by name, so automation and reporting keep working as expected.

The most reliable method is to create the deal directly from the existing contact or company record rather than creating it blank and associating it afterward — creating it “from” the record automatically carries over the right associations. If a deal comes in from an integration or another tool, it’s worth double-checking that it landed with a contact and company attached, since an unassociated deal won’t show up in that account’s history or in company/contact-level reports.

Yes. Beyond the primary contact and company, deals can be associated with line items/products, with other deals (useful for tracking renewals or split/carried-over deals so forecasting doesn’t count them as lost revenue), and with other custom records your portal may use for projects or tickets. These associations can be added, reviewed, or removed directly from the association panel on the deal record.

HubSpot’s product library lets you assign a SKU (a unique product code) to each item. It isn’t required, but it’s strongly recommended — SKUs prevent duplicate products, make it easier to match your product library to systems like your accounting or ERP software, and support more advanced automation down the line. If you don’t already have SKUs, you can create simple ones as long as each is unique per product.

Yes. When a product from the library is added to a deal, it becomes its own independent “line item” — essentially a copy of the library product. That copy can be freely adjusted (price, quantity, discount, description) at the deal level with zero effect on the master product record in the library. This keeps your library clean and standardized while still giving flexibility deal by deal.

Yes. The product library has separate price and cost fields, and permissions can be set so reps only see price, not cost. You can also add custom fields to the library (for example, a commission calculation field or a special pricing tier) that stay visible only to the people who need to see them, without touching what reps see day to day.

You don’t need real pricing to get value from it. Products can be created with $0 pricing — you’ll still get standardized names and descriptions, quantity tracking, and line-item-level reporting on deals; you simply won’t get an automatically calculated deal value from that item. This works well when pricing is finalized outside HubSpot but you still want visibility into what’s being sold.

Yes. Once products are added to deals as line items (rather than typed into a single deal-amount field), HubSpot can report at the line-item level — by product, by rep, by company, or by time period. This product-mix visibility is one of the main reasons to use the product library and line items instead of a free-text description or a lump-sum deal value.

HubSpot has native e-signature built into its quotes tool — a recipient can review and sign a quote without leaving the page it was sent on, included in your plan up to a monthly signature allowance. This coverage is limited to HubSpot-generated quotes, though; other documents (contracts, longer proposals) still need a dedicated e-signature tool like DocuSign or PandaDoc if those need to be signed too.

HubSpot generally treats an edit to a sent quote as a new version rather than a silent in-place change — each republish gets a new quote number/version, so everyone can tell which is current, and older versions stay available for reference. Depending on your approval process, an approved quote may also lock and require an explicit “recall” step before it can be edited again.

Either approach works. You can create products directly in HubSpot yourself, or if there’s a large list, it’s usually faster to fill out a product-import spreadsheet (name, description, price, SKU, etc.) and have it bulk-imported in one pass. After initial setup, day-to-day edits — new products, price changes, description tweaks — can typically be handled directly in HubSpot by your own team.

A sequence is a series of personal, one-to-one emails sent from an individual’s own mailbox — automatically personalized with that person’s name, signature, and meeting link, so it reads like a direct email from them. A marketing (nurture) email is sent in bulk to a list under a broader “from” identity and is meant for larger-scale outreach. Sequences tend to perform better for one-to-one selling since they feel personal; marketing emails are better suited for broad nurture campaigns.

Yes. Sending sequences — and even just viewing the Sequences tool — requires a paid sales seat. Free “core” or view-only seats can still own records and receive notifications, but they cannot send sequence emails or see sequence data. Anyone who needs to run sequences will need to be on a paid sales seat.

Yes. The system automatically unenrolls a contact from a sequence the moment they reply or book a meeting through a scheduling link in that sequence — you don’t need to remove them manually.

No. A contact can only be actively in one sequence at a time. If they’re already enrolled somewhere, they won’t be added to a second sequence until they finish or are removed from the first — worth planning for if you’re running multiple outreach tracks.

Yes. Sequence emails automatically fill in the sender’s name, email address, signature, and meeting link based on who is enrolled as the sender, so the recipient sees it as a direct email from that person. The message content itself is built ahead of time, but the sender-specific details populate automatically.

No. Sequences require a real, individual mailbox tied to a paid sales seat — a shared inbox or distribution list can’t be used as the sending account. A more generic “from” address is better suited to a marketing email than a sequence.

Yes. You can select multiple contacts from a list and enroll them in a sequence as a batch. There’s a limit on how many can be enrolled in one batch and on total daily enrollments, so bigger lists typically get worked through over several days.

There isn’t a single built-in “bulk unenroll” button. The reliable approach is to build a list of the contacts you want removed and use a simple automation (workflow) to unenroll them — that same automation can be reused any time a mass removal is needed.

Not automatically. Marketing email subscriptions and one-to-one sequence emails are tracked separately. Unsubscribing from a marketing list stops that category of bulk email, but it doesn’t by itself block a genuine one-to-one sequence email, since those are treated more like a personal email from a rep. If someone should be stopped from all outreach, that needs to be handled explicitly — for example, by removing them from any active sequence as well.

Yes. There’s a cap on sequence enrollments per sender within a rolling 24-hour period, though many teams intentionally send in smaller daily batches to protect deliverability and pace outreach naturally. This limit applies per sending mailbox.

This is almost always one of a few root causes: the enrollment criteria is narrower than expected (for example it requires a specific form, import type, or property value), the contact already satisfies an exit/“unenroll” criterion, or another workflow already claimed the contact and its removal logic is blocking re-enrollment elsewhere. We troubleshoot by pulling up the contact’s workflow history on their record to see exactly which criteria passed or failed, then adjust the logic so the intended path fires cleanly.

It depends on the automation type. Workflows can be configured to allow re-enrollment (often with a cooldown/eligibility window so someone isn’t re-triggered too soon). Sequences support being re-enrolled into a sequence they’ve already finished, but a contact can only be actively in one sequence at a time — enrolling them in a new one won’t happen while they’re already active in another.

Routing is typically built on criteria like territory/zip code, round-robin rotation, or existing account ownership, layered with exclusions (for example, skip auto-assignment if the contact is already a customer or came in through a specific channel). We build this as branching logic in a workflow so leads land with the right rep automatically, and it can be re-run manually if a lead needs to be pushed through again.

Yes. If one workflow’s “removal” criteria overlaps with another workflow’s enrollment trigger, a contact can get pulled out of a process before a downstream step (like a notification email) fires. The fix is usually to simplify the logic — either consolidate the overlapping workflows or add explicit exclusion criteria so they don’t step on each other.

No — disqualified or “current customer” status is normally added as an exclusion criterion so those records skip auto-assignment, sequences, and marketing sends. This exemption can also be set up to cascade from a company down to its associated contacts. One caveat: an exclusion status prevents automatic enrollment but doesn’t stop someone from manually enrolling that contact, so manual sends still need a quick gut-check.

Deactivating a user’s login doesn’t automatically clean up their fingerprints — any workflow step, notification, or record ownership tied to them keeps referencing that user until it’s reassigned. We handle this with a “find and replace” pass across all active workflows plus a bulk ownership reassignment, and we double check any connected integrations (like a CRM sync) that may have been running under that person’s credentials.

A third-party intent data provider tracks when companies are actively researching topics related to your product or service anywhere online (not just on your own website), then pushes matching companies and contacts into your CRM on a regular cadence. From there, a workflow watches for that signal (topic, score, and date) and automatically enrolls the matching contacts into a targeted email sequence. Most intent providers meter this activity with a credit allowance, so the workflow is usually tuned to a conservative daily volume to stay within budget.

Every contact record keeps an activity timeline that shows workflow enrollments and sequence activity, including the date and (for sequences) who enrolled them. For sequences specifically, there’s an “enrolled by me” type filter to trace individual sends. This is the first place we look whenever an enrollment looks unexpected or a “rogue” automation needs to be tracked down.

Yes — sequences automatically unenroll a contact the moment they reply or book a meeting, so they won’t keep receiving the remaining steps. Workflows can be built with similar logic (unenrolling on a meeting-booked event, for example), but for bulk marketing emails, automatic reply-detection doesn’t apply the same way — those rely on the unsubscribe link, so a courteous manual reply is sometimes still worth sending.

Yes — a workflow can trigger off almost any property change (a due date shifting, a deal stage changing, a file being uploaded) and send an internal notification with a direct link to the record, to whichever team members need to see it. The same pattern covers overdue-task reminders — a workflow can nudge the owner when something’s due and again if it’s still open a few days later.

Once a report is built with a rolling date range (like “start of this year” rather than a fixed calendar date), it recalculates on its own every day — so a year-to-date report always shows the current YTD total without any manual adjustment. If a report ever seems “stuck” on an old period, it usually means it was accidentally set up with a fixed date instead of a rolling one, and that’s a quick fix.

Yes — dashboards support a dashboard-level date filter that can control all the reports on it simultaneously, so you’re not adjusting each tile one by one. This works best when every report on the dashboard is built off the same underlying date field; if some reports use a different date property, they may not move in sync with the rest, so it’s worth confirming that during setup.

Dashboard visibility is controlled by your user permissions. If a teammate sees something you don’t, it’s typically because your account role doesn’t have the right access level yet. Your admin can either share that specific dashboard with your user or adjust your permissions so you’re looking at the same view.

This is usually a matter of what the report is actually counting. If a report is built on a property that lives on a related record (like a contact) instead of the record you care about (like the deal), you can end up with multiple rows per deal — one for each associated contact — which inflates the count even though the underlying dollar totals are still correct. Rebuilding the report to count the object you actually want (e.g., unique deals) resolves it.

Yes — any report, including the drill-down list behind a chart or number, can be exported to Excel or CSV. One quirk to watch for: exports sometimes show a company or contact name as a numeric ID rather than the actual name; there’s a report-level setting that can be turned on so names export correctly instead.

Yes — HubSpot’s tracked terms feature can flag specific words or phrases spoken during calls, which can then trigger notifications or feed into automation and reporting. It’s worth adding several phrasing variations for the same idea, since tracked terms match on exact wording and people phrase things differently.

Yes, as long as an industry or segment field is populated on your company or contact records, you can build reports that group and count records by that field. If older records are missing that field, it can often be backfilled or enriched so historical data is included in the segmented reporting too.

Yes — dashboards can be scheduled to email automatically on a recurring basis (e.g., every Monday morning) as a PDF snapshot with a link back to the live view. Keep in mind the emailed snapshot reflects data as of a set time, and a single scheduled email can’t show different filtered views to different recipients — if separate people need separate filtered slices, that’s set up as separate saved dashboards.

No — personal adjustments to a shared report or view stay local to you. To roll a change out to the team, you’d clone it and save it as a new shared version, or explicitly update the original and push it out. This makes it safe to tweak your own view without disrupting anyone else’s.

Yes — most chart-based reports support adding a trend line, which makes it easier to see the overall direction of a metric over time and can help highlight anomalies or spikes (for example, around a seasonal event or promotion) rather than just comparing period-to-period totals.

A segment (previously called a “list”) is a saved group of contacts, companies, or deals matching certain criteria — essentially your audience or dataset. A report visualizes or summarizes data — counts, totals, trends — often built on top of a segment or directly on record properties. A dashboard brings multiple reports together on one page. Segments can be “active” (automatically updating as records match or fall out of the criteria) or “static” (a fixed, one-time snapshot).

It depends on what they need to do day-to-day, not their job title. Reps working deals and sending sequences typically need a Sales Hub seat; service reps handling tickets need a Service Hub seat; people building campaigns and emails need a Marketing Hub seat. People who only need to view records, receive reports, or be listed as a record owner can often use a free seat instead of a paid one. We size each person’s seat to what they’ll actually be doing in the portal.

Yes. HubSpot offers free “view-only” seats for people who just need visibility — seeing records, receiving scheduled reports, or being assigned as a record owner — without needing to edit records or send communications. These free seats don’t count against your paid seat total, so they’re a good fit for managers, oversight roles, or team members who don’t need full editing access.

No. HubSpot has a free “partner” seat type specifically for registered agencies and outside partners working in your portal. It gives them the access they need without counting against your paid seat count.

Yes. This is controlled through permission sets combined with record ownership — you can set a rep’s default visibility to “records they own” or “records their team owns,” while managers and admins keep broader or full visibility. This can be configured separately for contacts, companies, and deals, and can incorporate manager/direct-report hierarchies.

Super admins have unrestricted access across the entire portal — including things a regular user (even the creator of an item) can’t do, like opening other users’ private/owner-only reports, managing all users and seat assignments, and changing account and billing settings. We recommend having at least one backup super admin on every account in case the primary admin is unavailable.

Deactivating a user frees up their paid seat so it can be reassigned to someone else. Any records they owned stay assigned to them unless you manually reassign them, and workflows, sequences, or notification emails tied to that user can start failing or stop sending. Before deactivating someone, it’s best to reassign their open records and use HubSpot’s “find and replace user” tool to swap them out of any workflows first.

Features like sequences are gated to specific paid seat types (for example, a Sales Hub Professional or Enterprise seat), not to admin status. Being a super admin controls what you can manage in the portal, but it doesn’t unlock tools that require a particular paid seat — the person still needs that seat type assigned to them to use the feature.

HubSpot’s built-in permissions control access at the record level (who can see or edit a deal/contact/company), not at the level of individual files or attachments tied to a specific stage. Restricting document access until a deal hits a certain stage — like blocking reps from downloading a contract until it’s fully executed — usually requires a custom setup layered on top of standard permission sets rather than an out-of-the-box setting.

Once your inbox is connected to HubSpot, one-to-one emails you send and receive log automatically to the matching contact record — no need to duplicate that work by re-entering them. Meetings booked through your calendar (Outlook, Google, or Teams) sync over as well. The main things that don’t log automatically are phone calls and emails sent from a shared/generic inbox that isn’t individually connected — for those, a BCC rule or the HubSpot sales extension can be set up so they land in HubSpot too. If emails suddenly stop syncing, the usual cause is the inbox connection dropping (a password reset, MFA change, or an IT security policy update) rather than anything wrong on the HubSpot side.

The sync works field by field: for each mapped property you choose a direction (HubSpot to Salesforce, Salesforce to HubSpot, or two-way) and, for two-way fields, a rule for what happens when values conflict. Updates typically flow through within minutes. Because HubSpot contacts map onto separate lead/contact objects in Salesforce, some fields need extra setup to land in the right place. If a record isn’t syncing, the most common causes are a deactivated integration user, a broken field mapping, or a record that doesn’t yet meet the criteria to sync (for example, a contact with no associated company).

A dedicated sending subdomain protects your main company domain’s reputation — if a marketing send ever runs into deliverability trouble, it affects the subdomain rather than the domain your day-to-day business email relies on. Setup just requires a few DNS records (typically for authentication standards like SPF and DKIM) added at your domain host; there’s no cost, and while HubSpot allows up to 72 hours for DNS changes to propagate, verification is usually done within minutes. Your reply-to address can still look like a normal company email even though the message sends from the subdomain.

HubSpot has tools that test inbox placement and show whether sends are reaching the inbox, landing in spam, or failing outright. The biggest factors are proper domain authentication, a clean send list (removing bounces, unsubscribes, and long-unengaged contacts before you send), and consistent, reasonable sending volume from an established domain rather than sudden spikes. If open/click rates are declining, a review of your suppression list and sending setup is usually the fastest way to find the cause.

Yes, HubSpot has a native QuickBooks Online integration that can sync contacts and products between the two systems. Product syncing works most reliably when each product has a consistent identifier (like a SKU) in both platforms — a product that only exists on one side won’t sync until it’s added to both. If you need more selective syncing (for example, syncing products but not invoicing), the native integration can be configured with filters, or a middleware tool can handle more custom scenarios.

It depends on what you’re signing. HubSpot’s native e-signature is built into the Quotes tool and covers simple sales documents well, with a generous monthly signature allowance included. DocuSign is generally the better fit for more complex contracts or paperwork outside of Quotes, and it can integrate with HubSpot so completed documents log back to the record automatically. If you’re already using DocuSign for other business needs, there’s usually no strong reason to switch just for HubSpot.

There are generally three paths: check whether the vendor offers its own HubSpot connector or a public API even if it’s not listed on HubSpot’s marketplace; use a middleware/automation tool (like Zapier) for lighter, workflow-based syncing; or, for larger and ongoing data needs, set up a scheduled file-based import/export process as a lower-cost alternative to a full custom integration. The right choice depends on data volume, how real-time the sync needs to be, and budget.

Yes — once your calendar is connected, externally booked meetings sync into HubSpot and log to the matching contact, using the meeting’s subject line as the title. If you log a meeting manually inside HubSpot instead, be sure to add a title, since manually logged meetings without one show up blank on the timeline. Booking through a HubSpot meeting link is also an option and lets you capture extra details at booking time.

Projects started in beta but has since graduated to a fully supported, permanent part of HubSpot’s CRM. Core CRM objects like this don’t get pulled once they’re generally available, so it’s safe to invest time in building your process around it.

Most commonly, a Project is set up to auto-create when a related Deal reaches a specific pipeline stage (for example, when a deal is marked “Closed Won” or reaches a stage like “Customer Evaluation”). That trigger stage can be changed, and you can add “on hold” or “paused” stages on either the Deal or the Project side so things don’t get lost if a deal or project needs to pause rather than move forward. Moving a project between stages (including back to an earlier one) is generally safe to do.

This isn’t automatic out of the box, but it’s a common automation to set up: assigning a Project owner can trigger all of that project’s tasks to be reassigned to the same person. Keep in mind that task due dates don’t automatically shift if the project’s overall timeline changes — that also needs a separate automation if you want it.

Yes. Ownership can be shown both in list/board views and directly on the record’s card, so you don’t have to open each one to see who’s responsible.

This can be configured to happen automatically as part of your setup — for instance, carrying attachments from a Deal over to the Project created from it, or automatically attaching a photo/file a customer includes in an email onto the Ticket that email generates. It’s not something HubSpot does by default across every object, but it’s a standard automation we can build in.

Yes. This is typically done with a dedicated file-upload property on the record — when a file is added to that property, it can trigger a notification to specific people and keep the file easy to find again later, rather than relying on someone remembering to check.

The top-level Stage and Status fields are HubSpot’s built-in defaults, so their label and position on the card can’t be changed or removed. However, everything else on the card can be customized, reordered, or made read-only, and in some cases you can add a Stage/Status view onto a related record’s card (like showing project status on the associated deal) with the right permission setup.

The Tickets object is a core part of HubSpot and can’t be fully deactivated. If you’re not using it for its default purpose, you can leave it inactive with no real downside, or repurpose/rename it for a different process — several accounts end up with a few unused default or custom objects like this.

In most cases, yes. Your QBS consultant can set you up with a trial or demo environment so your team can explore before anything goes live in your production portal. Keep in mind a sandbox is typically a blank slate rather than a full mirror of your live account, and access is often time-limited rather than permanent. If a dedicated sandbox isn’t practical for your situation, your consultant can instead walk you through a live demo using sample data.

Most onboarding plans include a short series of sessions rather than one long walkthrough — for example, a session on the core platform, a session on day-to-day workflows (including mobile use), and a session for Q&A and more advanced topics. Your QBS consultant will share a written agenda ahead of each session, and there’s often a bit of “homework” in between so your team can practice before the next one. The exact number and focus of sessions is tailored to your build and rollout plan.

Your QBS consultant will give you an estimate up front for larger builds or projects. If a session runs long due to troubleshooting on our end rather than added scope, that time generally isn’t counted against your hours. If a project looks like it will need meaningfully more time than planned, your consultant will flag it and talk through options with you — such as drawing from a flexible bucket of hours or adjusting scope — before moving forward. Unused hours at the end of an engagement can often be applied to a future project.

After most sessions, your QBS consultant sends a recap summarizing what was discussed and any outstanding items — both what QBS owes you and what’s needed from your team. If you ever feel like something slipped through the cracks or you didn’t receive a recap, just ask your consultant to resend the outstanding-items list; it’s often just a matter of getting the right people added to the distribution.

Yes, sessions are generally recorded with screen share included. Your QBS consultant can send you the recording link once it finishes processing, which usually takes just a few minutes after the call ends. If a specific team member’s calls aren’t generating a recording, let your consultant know — it’s usually a quick settings fix on that user’s account.

Yes. Additional or refresher sessions can be scheduled as needs come up — for example, ahead of a new feature rollout or after a change in your team. You can also bring in specific people, such as early adopters or “champions,” to join an existing working session rather than waiting for a full team training. Just let your QBS consultant know who you’d like included and what you’d like covered, and they’ll get it on the calendar.