topic Re: Modules Issue from Page Import Via API in APIs & Integrations

Modules Issue from Page Import Via API

tmcmillan99 — Fri, 18 Jul 2025 14:32:25 GMT

I'm using the API to import a batch of pages. The import is successful but I seem to have a disconnect with the modules once the pages are in the portal. I get the following attached error when viewing the modules in the page edit mode. Not sure what I am missing on the import. The file was created by exporting it out of another portal then adjusting the json so it could be used for the import. Both portals are using the same theme.

Any suggestions on what I need to review in order to fix the module disconnect?

Also, should the page template urls in the import json file point to the main theme or the child theme?

Thanks,

Terry

Re: Modules Issue from Page Import Via API

FaramarKolivand — Fri, 18 Jul 2025 15:49:36 GMT

Is the module path in your JSON matching with the exact path of the module in the destination portal? Also verify the theme and its modules are installed and piblished. If you're using a child theme then your template url should point to your child theme as well.

Re: Modules Issue from Page Import Via API

tmcmillan99 — Fri, 18 Jul 2025 16:12:11 GMT

@FaramarKolivand
The json file doesn't contain paths for the modules. It has a reference to them by label, name, and id. I guessing the name and id are going to be diferent depending on the portal the module is in. The labels match the modules correctly. Not sure how Hubspot is referencing the modules since the path is not included when you produce the json file with the API Get command. Maybe from the page template url which tells it the theme to look at? Currently, I have the page template url pointed to the child theme in the portal that I am importing into.

Re: Modules Issue from Page Import Via API

FaramarKolivand — Fri, 18 Jul 2025 17:29:02 GMT

That's correct, HubSpot assign unique IDs per portal, so the ID and name values can be different between portals even if the labels match. If you run a GET in the destination portal, you should be able to get the correct ID and name, no?

Re: Modules Issue from Page Import Via API

RubenBurdin — Mon, 18 Aug 2025 17:19:33 GMT

You’re right, @tmcmillan99

This usually comes down to HubSpot assigning unique IDs per portal. Even if the labels look the same, the underlying name and id values from your source portal won’t map cleanly once you import into a different one.

That’s why after exporting, you’ll need to run a GET request for modules in the destination portal to grab their actual IDs and update your JSON before re-importing (docs here: https://developers.hubspot.com/docs/guides/api/cms/source-code

On the theme question: if you’re working off a child theme in the target portal, your page_template_url should point there. HubSpot resolves modules relative to the active template https://developers.hubspot.com/docs/guides/api/cms/pages

Also double-check that all modules are published and paths align in the new portal. If any module is missing or unpublished, HubSpot can’t resolve it and you’ll get that disconnect error.

Cross-portal imports tend to be brittle because IDs aren’t portable. The clean fix is always to fetch fresh IDs from the target portal and adjust the JSON accordingly.

Hope that clears it up, let me know if that makes the error go away.

Re: Modules Issue from Page Import Via API

tmcmillan99 — Mon, 18 Aug 2025 18:54:21 GMT

@RubenBurdin Thanks for the followup reply. Makes total sense concerning the ids on the modules. The next time I do the export/import, I will do your suggestion in updating the module ids from the new portal.

Thanks,

Terry