Great minds think alike

As a HubSpot admin who participates in weekly product update reviews, I need a native Product Updates object that surfaces beta and release data as CRM records, so that I can track evaluation status, communicate adoption decisions with my team, and demonstrate feature adoption over time, without manual data entry or external tools.   The Problem: HubSpot releases a significant and sometimes overwhelming number of product updates weekly across multiple hubs and product areas. While the Product Updates portal is excellent for discovery, there's currently no way to: - Track which betas or releases your organization has evaluated or joined - Create a structured, searchable record of evaluation decisions and timelines - Report on adoption patterns to leadership or during renewal discussions - Automate team communication about beta participation status - Maintain institutional knowledge about why certain features were pursued or deprioritized   The Solution: A native Product Updates object (similar to existing objects like Campaigns or Marketing Events) that automatically syncs publicly available product update data from HubSpot's Product Updates portal. Key fields would include: - Title, description link, and knowledge base article link - Rollout state (LIVE, PUBLIC_BETA, PHASED_ROLLOUT, etc.) - Release date and stage transition date - Hub and feature area categorization - Impact level (MAJOR, MODERATE, NOT_SIGNIFICANT) - Type (INITIAL_RELEASE, REDESIGN, BREAKING_CHANGE, SUNSET, etc.) - Whether it includes AI features - Rollout enrollment status Teams could then layer their own tracking properties: - Evaluation stage (Reviewing, Testing, Implemented) - Participation status (Requested, Joined, Not Pursuing) - Internal owner and decision notes - Last reviewed date   Business Impact: 1. Renewal and Expansion Evidence: CSMs and account teams can demonstrate concrete adoption of new features and expansion of HubSpot usage over time, strengthening renewal conversations. 2. Product Feedback Signal: HubSpot gains structured data on which betas resonate with customers, which are ignored, and why, which informs product prioritization. 3. Expansion Opportunities: When an account shows strong evaluation activity in one hub but hasn't expanded into another, it becomes a natural conversation starter. 4. Team Alignment: Reduces friction around communicating beta participation decisions across technical, marketing, sales, and service teams. 5. Operational Efficiency: Eliminates redundant manual data entry and tracking across disconnected tools.   Why This Matters: HubSpot's own customers are your best advocates for product adoption and expansion. Making it easy for them to track, evaluate, and demonstrate adoption of new features turns the Product Updates experience into a built-in sales and retention tool, not just a discovery channel. ...read more

I'm working on a project that started with Production and a Legacy Sandbox. A lot...and I meant almost a full year...of changes went into that Sandbox. We used a 3rd party tool to attempt to move all the customization and configuration to Production. It wasn't great, but we worked through all the issues and misses.   Once Production was validated we created a new Standard Sandbox. Which was very disappointing because a large amount of the customization that has now been built twice (once in Legacy Sandbox and again in Production) did not show up at all in the new Sandbox.   I welcome all HubSpot users to use this thread to ask for a 100% replica of Production when building Standard Sandboxes going forward. Please use this thread to note anything that gets missed when you build your Sandbox and ask HubSpot to account for it.   The new Standard Sandboxes do not bring custom layouts down to the new Sandbox. This is a HUUUGGEEE miss for the project I'm currently on. We have massively configured Team layouts for Deals and so many Custom Objects.    While I'm pointing out things that are missing:   Teams Also the rules for which Teams can update certain properties were removed because there are no Teams? Now I have to go through approval properties with a fine tooth comb or risk overwriting them in Production when I deploy back? This has yet to be determined. Permission Sets Notification Presets In this particular custom solution and configuration, we relied on these items and their capabilities to provide a solution to the client. To have them ignored and having to spend time rebuilding them for a 3rd time is not going to be a fun conversation to have with the client. ...read more

The new Beta feature for Calendar View in Deals is great, but I would like to have a Calendar view in my Custom Objects. I know there is an App in the Marketplace that does this, but I wonder why it exists for Deals and not Custom Objects.    ...read more

HubSpot recently released the ability to ASSOCIATE Leads and Custom Objects. I want to extend this functionality, so that we can CREATE Leads from Custom Object records.  I spoke with HubSpot Support about this, and the main obstacle is that the Lead must be associated with a Contact or Company, not just the custom object. My proposal for this is that the Create Lead form would include a required association to either a Contact or Company record. We see this object association option in other object creation forms.  ...read more

We need the ability to append custom single-line and multi-line text values when merging records or in a workflow (where the "append" option is missing).   As an agency, we use a custom text property to house Partner IDs for our brands inside different PRMs, but we often run into the case where major publishers have multiple IDs; since we use it as a unique identifier, this creates duplicates that, when merged, remove the alternative IDs that we need to see.   Some publishers will use a dozen or more Parner IDs and we need to see all of them in their company records.   Currently, the only solution is to review the history of the property and append the values manually (which is too time-consuming to sustain as a practice), or download our duplicate companies every week or two and append the values in a spreadsheet, then import them back into the system and proceed to merge the duplicate records.   Neither of these solutions are what you'd expect from a professional CRM like HubSpot, and we need a better way.   It would also be great if we could retrive and append values from a property's history in a workflow as well. ...read more

Native objects and custom objects are in the mobile app. This should be the same for on-demand object  (appointments, Projects, Services, Listings and Courses). ...read more

The ability to assgin an owner on a round robin basis, controlled by a multiple user field. Example, Custom Object Record has 3 users selected in a "Sales Reps" - User field. A deal is created & associated to the Custom Object Record. Assign the deal owner to one of the "Sales Reps" on a round robin basis ...read more

Currently, when using the Global Search Function, we cannot amend the default Global Search Results Settings to display properties in the Global Search Results View columns that are relevant to the specific business, and customise views to different teams/ team members in the business.    i.e. Global Search Results for Contacts only show default columns for Name, Email, Phone number, Primary company, and job title.  Global Search Results for Companies only show default columns for Company Name, Domain, City, Region, Phone and Company Owner.  Similarly, we are locked to default properties with Deals, and all other objects.    Goal  We are able to tailor the Global Search Results settings to meet the needs of different teams/users, much like the way we already can edit the object-specific search result views with the Contact/Company/Deal search tabs. This will enable us to:  - Choose properties to display in the Global Search Results view  - Choose order of columns that display  - Change length of column.   Different teams have different needs:    Use cases Different properties/columns to display for different teams  - Service teams may find it more useful to see a customer code property/column in the Global Search Results View; while they can use the Global Search to find the correct company, they can't see on the screen they are clicking on the correct company, because we cannot bring in the <CUSTOMER CODE> company property to the results view.  - If searching companies, would be great for sales teams to see the primary contact in a column, and click directly onto this, rather than needing to click on the company record, to then search for the primary contact  - If searching tasks, would be great to see the internal task owner in a column, so you can easily see accountability.    Ability to edit length of columns  There may be several entities e.g. deals, companies, with nearly identical names, but a small variation right at the end of the deal/company name. So we can correctly read the name, we need to be able to edit the length of 1 particular column in the display screen. This means we don't have to click into the record/hover over each record, to read it. e.g. COMPANY NAME is likely to be longer than other properties, so we want the ability to make this column longer than others.    ...read more

The introduction of Prospecting to manage leads is a welcome addition to HubSpot.  We have adopted it and over all it works really well.   However, some of the standard functionality in how you manage other record types (companies, deals and contacts) aren't available for Lead records.  This includes: exporting leads to a spreadhseet, and the ability to make wholesale changes to that export and re-import it back into HubSpot.  The ease of use of HubSpot doesn't seem to apply to Lead records which is frustracting and hard to understand.  Can this be fixed to make data management of lead data easier and encourage the adoption of the Lead feature in HubSpot?   ...read more