Migrating WordPress custom post type

Nick-W — Thu, 04 Jan 2024 15:33:44 GMT

I read that dynamic pages can be created on a HubSpot hosted website using either the HubDB or a CustomObject. Currently 'Products' are setup as a custom post type in WordPress (there's no ecommerce involved) and each product includes several images, custom data fields, and several PDF downloads.

What would be the best strategy when it comes to migrating to a website hosted by HubSpot?

Would each dynamic 'product' page have it's own SEO friendly url?

Could product categories and category filters be added?

Re: Migrating WordPress custom post type

Anton — Sat, 06 Jan 2024 09:59:43 GMT

Hi @Nick-W,

TL;DR: yes it's possible.

The big question is: How you would like to solve it and what subscription you have.

Short run-down comparison:

HubDB is available in CMS Profesional and Marketing&CMS Enterprise.
It's great for display a non CRM relevant type of content
It's limited to 10k entries per table(you can create child-tables)
You can display only 200/250(not sure) entries per call/page
are filterable with a bit of custom code
They're easier to maintain for non-devs since there's a new visual editor
....

Custom Objects are Enterprise exclusive
Great for CRM related things
"unlimited" size
Accessable through workflows
Are filterable with a bit of custom code
...

If you want to learn more about both - @Teun and I had our first Developer HUG exactly about this topic. Here's the youtube link to From Stagnant to Scalable: Powering Web Content with HubDB and Custom Objects.

Both options have the ability to create custom URL-structures like

DOMAIN.com/products-overview

DOMAIN.com/products/category-1

DOMAIN.com/products/category-1/product

Another function you could use is the blog. Yes - the blog.

Think like this: The blog overview page is your Product overview page. It's gonna generate automatically with the cards/products(or whatever display option you will go with). Every blog post is a single product. The tag pages are your (sub-)category pages. The blog tags are your filter options.

But there are a few minor drawbacks:

It's not possible to to create custom category URLs. They always will be like DOMAIN.com/products/tag/category-1 - - - in this case "products" is the slug/name of the blog. HubSpot adds the /tag automatically and there's no real workaround it.
While the blog listing and blog post templates have drag&drop the category pages are automatically generated with the layout you create - you don't have the ability to move things around or modify layout/content per page(unless you want to create every tag page manually - something I really don't recommend)

About your question "what's the best strategy...?"

I'd suggest to start by writing down all needed function like

Product image -> image field
Product name -> text field
Product description -> text field / rich-text
...

after that create custom modules with the desired layout for the module - not necessary but helpful

Write your templates for listing, category and post/single product

Here are some helpful resources:

Dynamic pages with HubDB and Custom Objects
For-loops (repeater)
Filters
Module and Theme fields

best,

Anton

topic Re: Migrating WordPress custom post type in CMS Development

Migrating WordPress custom post type

Re: Migrating WordPress custom post type