Moving Content Between Accounts
When you open a second account — for a new brand, a new region, or a separate project — part of the content can be moved from the existing account, and part has to be created again. This article lists both.
NoteThis article covers moving content between two Yespo accounts. If you are switching to Yespo from another marketing platform, see Migration.
What Can Be Moved
Email Templates
Email templates can be copied to another account. There are two ways:
- Copy to another account. Available for message templates to users of the main account: open the message list, use the message's menu, and select the target account. This keeps the template structure intact.
- Transfer the HTML. Open the message in the editor, export or copy its HTML, then create a message in the target account and paste the HTML in. Use this when the accounts are not linked to the same main account.
After the transfer, check the parts of the template that reference account-specific objects — the sender, subscription categories, links to a custom short-link domain, and any personalization that reads custom fields. These are resolved against the account where the message is sent, so they have to exist in the target account too.
Custom Fields
Custom fields are moved by re-creating the field structure and then importing the values:
- In the source account, export the contacts together with the custom field columns.
- In the target account, create the same additional fields — the same names, types, and lists.
- Import the exported file and map each column to the corresponding field. See Uploading a File with User Profile Data.
Field IDs are assigned per account, so they will differ in the new account. Update any integration, SDK call, or velocity expression that refers to a field by ID rather than by name.
What Is Not Moved
The following objects are configured again in the new account:
| Object | Why |
|---|---|
| Workflows | There is no self-service transfer of workflows between accounts. Rebuild the workflow in the new account, selecting the messages, segments, and events that exist there. Support can be asked to move a workflow, but this is a manual operation and is not guaranteed. |
| Domain and sender settings | Domain verification, DKIM and SPF records, senders, and the short-link domain are bound to the account. Repeat the setup — see Setting Up Email Domain Authentication and Adding/Changing/Deleting a Sender Name. |
| Event types | Event types are registered per account. Create them again and repoint your integration to the new account's API key. |
| Segments | Segment conditions reference account-specific fields and events, so they are recreated in the new account. |
Recommended Order
- Verify the domain and add senders in the new account.
- Create the additional field lists and fields.
- Import contacts with their custom field values.
- Copy or re-create the message templates and check their senders and personalization.
- Register event types and switch the integration over.
- Build the segments, then the workflows.
Related Articles
Updated 35 minutes ago