On this page
What HubSpot supports natively
| Route | Between | What copies | Not copied |
|---|---|---|---|
| Multi-account management | Accounts in one organization | Form name and fields; missing custom properties are created | Submission data |
| Partner Portability (beta) | Partner account → managed client | Form name and fields | Anything beyond names and fields isn’t described as copied |
| Sandbox deploy | Standard sandbox → its production | Newly created forms | Edits to existing forms; form settings must be reconfigured |
Within one account, you can clone a form. Between accounts that aren’t linked in one of these ways, HubSpot has no form copy.
How to copy a HubSpot form to an unrelated account
- List the properties behind every field. Each form field writes to a property. Note the internal name, field type and, for dropdowns and checkboxes, the internal option values.
- Create those properties in the destination with the same internal names and option values. A field whose property doesn’t exist can’t be added. See how to import custom properties from another portal.
- Rebuild the fields and layout. Recreate field groups, required flags, placeholders, validation and dependent-field rules.
- Redo the settings. Notification recipients (owners and teams differ by account), follow-up emails, the redirect or thank-you message, consent and subscription types, and the form language.
- Reconnect what used it. Workflows triggered by the old form, segments filtered on its submissions and pages that embed it all need pointing at the new form.
- Swap the embed codes on your site and submit a test.
Common mistakes
- Different option values. A dropdown with the same labels but different internal values breaks workflow branches and list filters that check it.
- Forgetting the workflow. A form-triggered workflow doesn’t follow the form; copy it separately and point it at the new form.
- Leaving the old form live. Old embeds keep sending submissions to the source account until you replace them.
Where Jetstack AI fits
Jetstack AI’s Portal reuse copies forms between any two connected portals with their fields, field groups and redirects, and remaps properties, option values, notification owners and teams for the destination. Review follow-up workflows and dependent-field logic after deploying, and deploy properties before forms: a field whose property is missing is left out. You can roll back a Portal reuse deployment: Jetstack shows you what will be removed first, then deletes the assets that deployment created in the destination portal. It won’t delete anything another deployment or Project still uses, and it skips assets that were changed after the deployment. You can deploy the same setup to multiple destination portals, reviewing each portal’s mappings. See the forms reference.
Sources
- Copy assets to another HubSpot account (HubSpot Knowledge Base)
- Copy partner assets to client accounts (HubSpot Knowledge Base)
- Assets eligible to be deployed to production (HubSpot Knowledge Base)
- Forms (Jetstack AI documentation)
Checked October 29, 2026. HubSpot changes its products often; tell us at team@jetstack.ai if something here is out of date.
Copy & migrate between portals
Take a proven setup to the next portal.
Import a setup with its dependencies, map it to the destination portal and deploy it with references rewritten.
Explore Portal reuse