Seeking ideas to help with the case studies tool deprecation

The announcement that case studies tool is deprecating in a little over a month has been stressful, and I welcome input on our objectives below. The auto-migration to the blog is not acceptable for how we want to present case studies, so I will need to make some decisions and manually migrate to a new case studies solution.

There are several key aspects of case studies that are negatively impacted:

  1. Having a sortable case studies portal page that lists cards/tombstones across case studies. This gives visitors a quick look at ‘wow, all those case studies’. No one will likely read every one, but seeing them all on the main case studies page is key.

  2. Maintaining the URL structure we currently have in the tool, so that it preserves current links/backlinks, and can be built on that same structure going forward. Integrating with our blog breaks that. These links are in our ad campaigns, CTAs, funnels, third party pages, and backlinks. We have had a structure of domain.com/case-studies/case-study-1 . with the /case-studies/ being the sortable main page referred to above.

  3. Our product is a platform with multiple modules/products, so we have case studies focused on implementing product 1, product 2, etc. And would like to make them sortable, in some fashion, by that tag.

  4. The auto-migration of case studies into the primary blog, as mentioned in the deprecation notice, would seem to scatter case studies across all of our 100s of blogs, listed chronologically, and not have a dedicated landing page. There are a number of touches we might want to have on a case study page that differ from what we have in our blog, with its sidebar and ‘next article’ recommendation engine, etc.

I’ve heard that a possible solution is:

  1. set up a 2nd blog that is solely dedicated to case studies.
  2. Leverage tags on the ‘listing’ page for that blog, for people to sort only from case studies

Is it possible to find a listing page template that is set up for a matrix or grid display of case study cards/images, that won’t cost a heavy price for custom dev? Something that has a similar look to HS current case study main page.

Are there other solutions/nuances to consider?

Hey @donrua,

Thanks for posting here! The tight timeline here is understandable and I truly appreciate your adaptability. As you have a couple of suggestions already I’m going to leave it to the community to see if they have any experience with or any thoughts they’d like to share.

Here are a few resources you may find helpful in the meantime:

Curious how others structured this after the deprecation announcement. Hey @danmoyle, @CarolinaDeMares, @CGrove5 – do you have any suggestions for @donrua on this?

Thank you in advance! :raising_hands:

Sam, Community Manager

Hi Don, the auto migration to blog posts loses the parts that make a case study page useful, so moving to HubDB is usually the cleanest fix. Create one HubDB table with a row per case study and columns for industry, product, company size, logo, summary, metrics and a rich text body. Then build one dynamic page from that table: the listing view becomes your sortable portal with filters on those columns, and each row gets its own detail page and URL. Export your existing case studies first, map them into a CSV with those columns and import it, so the manual part is mostly copy and paste. Keep your current URLs by setting the dynamic page slug to match, or add 301 redirects. If you need gating or forms, put a HubSpot form module on the detail template.

hey @donrua Before you rebuild anything, check what the migration actually does, because it covers more of your list than it seems. Per HubSpot’s KB (on December 12) published case studies become published blog posts at their original URLs, the case studies listing page becomes a blog listing page, and language variations carry over: knowledge.hubspot.com/website-and-landing-pages/create-and-manage-case-studies. So /case-studies/ and your individual case study URLs should keep resolving.

That makes your option 1 the low-effort path, with one thing to check after the move: templates are set per blog, not per post. If the case studies land in their own blog, give it a card-grid listing template and use tags for each product. If they land in your main blog, they’ll pick up its templates, and you’d move them into a separate blog to get the grid layout without changing your main blog.

If you need richer filtering (product plus industry at once), HubDB dynamic pages are the stronger option, on Content Hub Professional or Enterprise: knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables. After the migration the blog owns those /case-studies/ URLs, so you’d unpublish it and 301 to the HubDB pages.

Do you need people to filter by one product at a time, or combine filters?

@donrua +1 to this! Due to the format you need, this might be the best approach.
It might take some time to set up (manual work) plus you will probably need a developer’s help with the templates (I can help you, feel free to DM me), but it will allow you to meet the criteria you ask for.

Thanks everyone, and Uttam’s point is a good one since the migration keeps your URLs. A quick way to decide: if a card grid with one filter, like product tags, is enough, keep the migrated case studies in their own blog with a card listing template. If you need to filter by several things at once, like industry and company size, or show metrics on each card, that’s where HubDB earns the extra setup. Either way you only need one template for the listing and detail views. If you go the HubDB route and want a head start, I can share a simple listing and detail template outline, just send me a message.

@donrua

We were also using the Case Studies tool, so we’re facing a similar situation with the upcoming migration.

We’re planning to create a separate blog dedicated to case studies, with custom listing and post templates, along with a filtering module to give visitors the experience they need.

You can actually take filtering further than standard blog tags. With custom modules using HubL or GraphQL, developers can group tags into different categories (such as Product, Industry or Topic) and build multi-dimensional filters, while keeping the content managed as native blog posts.

Of course, this approach requires some development, particularly for the custom grid layout and filtering. Depending on your existing theme, you might already have a listing template that could be adapted, which could help keep costs down.

We won’t be using HubDB for this particular use case. It’s excellent for structured datasets and dynamic content, but since case studies are editorial content, we’d rather take advantage of HubSpot’s native publishing functionality and keep the process straightforward for the marketing team.

We’ve used similar approaches on other HubSpot websites, and the key is separating how content is managed from how it’s presented to visitors.

Hope this gives you another option to consider!

Thanks, Harsh. I assume all that would be great, but I’m not a developer and don’t have devs for web/marketing. I may try to walk it forward step by step with AI help, but not an area I’m familiar with, and I would not want to write responsive css for a new listing/layout portal, even if the data was in a db.

I have a basic hubdb and front page a dev built for me years ago, but it doesn’t connect to the case studies being build in a blog. They would be built with standard web templates in the cms web page section. Were you suggesting combing the above hubdb approach with a blog, or just with standard web pages?

Thanks, Uttam. This makes me hope, but I haven’t seen confirmation that all of our urls will stay exactly the same so backlinks, ctas, funnels all operate with them. Our current blog is on a different subdomain, but maybe the HS migration plan doesn’t do that. I’ll check the pages again, my first look, I couldn’t see concrete answers to the urls, nor what the listing page might look like.

We prefer the portal, tiles type of front page for the case studies area. Sorting by our product modules would be helpful, but being able to combine product with industry label would be better, but optiona. i.e. “All case studies in Sports vertical with Recover module”

stassey - I checked the link to the templates but onlyh saw one item for Listing page. Not sure what to do with it, not a developer, but is there a listing page designed to look more like the case study tile page that was being used for the sunsetting beta? That’s the style I want, and was hoping the devs in charge o fthe migration might provide something, or if there is something like that available. I dont’ really know how to build something specifically for a blog listing page, with the tiled style, but if there is something out there available from HS, or marketplace, I’d love to take a look at it.

Stasey, some questions.

Uttam suggested all the urls will stay the same in the migration. That’s preferable for my funnels, ads, backlinks to case studies.

So, to use specifics.

We have an existing blog at a subdomain, blog.getadmiral.com…but that subdomain and url won’t be used in any way as part of the migration, yes/no?

As part of your migration, you will set up a 2nd dedicated blog for us, at a new url to match the current case studies location www.getadmiral(dot).com/case-studies, true or false?

Each case study is currently at www.getadmiral.com/case-studies/case-study-1-name so those urls will be kept intact as for the case studies, but will be built in a blog cms tool? And each new case study I build there, will continue the same url structure within the case-studies path?

What can I expect for styling/layout/css for this new blog? Will it use our css from our current blog, or our main site. There would likely be no css classes built for this new blog, not sure how the styling maps.