How to copy assets across workspaces

Copy a journey map or template into another workspace, even one in a different account you belong to, and share personas through the Account Library.

Copying an asset makes an independent duplicate of it in another workspace while the original stays where it is. Journey maps and templates have a direct Copy to other workspace action; personas travel through the Account Library instead. If you want a single shared item that stays in sync across workspaces in one account rather than separate copies, use the Account Library.

---

How to copy a journey map or template to another workspace

Journey maps and templates use the same Copy to other workspace action on their row's three-dot menu. The steps below are for a journey map; copying a template is identical, started from the Templates list instead of Journey maps.

1

Open the journey maps or Templates list in the source workspace

In the workspace that holds the item, click Journey maps (or Templates) in the sidebar.

2

Open the item's three-dot menu and click Copy to other workspace

On the row for the item you want to copy, open the three-dot menu and select Copy to other workspace.

Journey map row menu > Copy to other workspace

3

Tick one or more destination workspaces

The picker lists the workspaces you can copy into, grouped by account, so workspaces in other accounts you belong to appear here too. Tick each destination you want. The source workspace is not offered.

Choose one or more destination workspaces

4

Click Copy to workspaces

Copy to workspaces stays disabled until at least one workspace is ticked. Clicking it duplicates the item into each destination you selected. The copy opens from the Journey maps (or Templates) list in that workspace.

Important: Copying a journey map leaves its linked data behind

A copied journey map carries only the content that lives on the map itself. Its linked personas, portfolio items (opportunities, pain points, solutions), tags, and metrics are not copied to the destination workspace, and personas have to be reassigned there.

If you need that linked content to travel with the map or stay in sync, add it to the Account Library instead of copying.

---

Copying personas to another workspace

Personas have no direct cross-workspace copy. A persona's row menu offers Make a copy, which duplicates it within the same workspace, but no Copy to other workspace.

Persona row menu > Add to account library

To use a persona in another workspace, click Add to account library on its row. The persona becomes a single synced item available across every workspace in the account. For the full flow, see How to use the Account Library.

---

Copy vs the Account Library

Both put an asset in more than one workspace, but they behave differently once it's there. Pick by whether you want the copies to drift apart or stay identical.

• Copy to other workspace - Makes an independent duplicate. Each copy is edited on its own and the versions drift apart over time. Works for journey maps and templates only.

• Account Library - Keeps a single shared item. Editing it in one place updates it everywhere it's used. Works for journey maps, personas, portfolio items, metrics, and templates, within one account.

	Copy to other workspace	Account Library
Best for	A starting point you'll change independently per workspace	One source of truth shared across workspaces
Stays in sync?	No, copies drift apart	Yes, edits propagate everywhere
Carries linked data?	No, personas and portfolio items are dropped	Yes, a map's linked items move with it
Across accounts?	Yes, into any account you belong to	No, one account only

For how the Account Library works, see How to use the Account Library.

Related topics

How to use the Account Library

Share a single synced item across all workspaces in your account.

How to create a workspace

Add a new workspace to your account.

How to create and use templates

Save a journey map as a template and start new maps from it.

How to manage workspaces

Rename a workspace or delete it permanently.