On this page
What HubSpot supports natively
A list has two parts: its definition (name and filters) and its members (the records). HubSpot copies the first between linked accounts. It never copies the second.
| Route | Copies | Doesn’t copy |
|---|---|---|
| Multi-account management | Segment definition | The CRM records in the segment |
| Partner Portability (beta) | Segment names and filter criteria | Records |
| Sandbox deploy | New active and static segments using property, membership, workflow enrollment and some marketing interaction filters | Edits to existing segments; segments using import membership, form submission, legacy behavioral event, legacy CTA or marketing event filters |
| Import tool | Records; for contacts, “Create a contacts segment from this import” builds a segment of the imported rows | The original segment’s filters |
How to copy a list to another account
For an active list (filter-based):
- Note every filter: the properties, option values, forms, emails, pages and other lists it checks.
- Make sure those exist in the destination with the same internal names and option values.
- Recreate the segment with the same filters, pointing each one at the destination’s version.
- Compare the member count with the source once the destination has its records.
For a static list, or a company list you want to keep as is:
- Export the list’s records from the source account with the properties you need.
- Import them into the destination. Contacts match on email and companies on domain name, so existing records update instead of duplicating.
- For contacts, tick “Create a contacts segment from this import”. For companies, build a static segment from the imported records afterwards.
Common mistakes
- Nested lists. A segment filtered on membership in another segment needs that segment copied first.
- Email and form filters. “Opened email X” or “submitted form Y” filters point at assets that have new IDs in the destination.
- Expecting the count to match on day one. An active list only matches the records the destination actually holds.
Where Jetstack AI fits
Jetstack AI’s Portal reuse copies list definitions with their filter tree, remapping properties, option values, owners, pipeline stages, forms and nested lists, and reuses a destination list with the same name instead of duplicating it. Static lists arrive as manual lists without members, and you should check dynamic list filters in the destination after deploying. It doesn’t move records. 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 lists reference.
Sources
- Copy assets to another HubSpot account (HubSpot Knowledge Base)
- Assets eligible to be deployed to production (HubSpot Knowledge Base)
- Import objects (HubSpot Knowledge Base)
- Lists (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