Transferring Data and Content Between Accounts

Yespo has no single tool that moves the whole contents of an account. The dedicated cross-account transfer feature covers message templates only. Contacts can be moved by export and import, and the rest of the data and settings have to be recreated manually.

Everything else is done the same way as a regular migration. If you are moving to Yespo from another marketing platform, see How to Migrate to Yespo from Other Platforms.

What Can and Cannot Be Moved

Copying a Message Template to Another Account

The feature creates a copy of the selected message's template in the child account, keeping the template structure intact. It works for messages of all types.

Copy to another account is available to users of the main account, and the target account has to be a child of it — ask support to link the accounts if it isn't. Open the message list, use the message's menu, and select the target account.

Copy templates one at a time: copying templates to another account in bulk isn't supported.

The template is copied together with its language versions and the images used in it. Reusable modules, tags, and categories are not carried over, and neither is the source account's image gallery: recreate the modules, tags, and categories, and re-upload the images to the target account's gallery if you need them there.

After the copy, check the settings that apply to that type of message:

• the sender and the other channel settings — they belong to the account and have to be set up again;
• for email — the unsubscribe link, subscription categories, links that use a custom short-link domain, product recommendation blocks, and external data sources: they reference the configuration of a specific account;
• personalization that reads custom fields. Field IDs are assigned per account, so any integration, SDK call, or Velocity expression that refers to a field by ID rather than by name has to be updated.
• that every image in the message still renders.

Transferring the HTML Instead

If the source email was built as custom HTML, copy its code and create an HTML email in the target account. This also works between accounts that are not linked to the same main account.

Transferring the HTML doesn't reproduce the drag-and-drop editor structure, reusable modules, comments, language versions, or other template-level settings. After the transfer, check the email in the editor and send yourself a test.

What Else You Might Move

Contacts. Export them from the source account and import the file into the target account. See Uploading a File with User Profile Data. Handle subscription statuses separately: a plain contact import can create active contacts out of people who had unsubscribed, complained about spam, or become undeliverable. See How to Migrate to Yespo from Other Platforms for the correct procedure.

Custom fields. There is no automatic copying of custom fields between accounts. Recreate the structure, then import the values:

1. In the source account, export the contacts together with the custom field columns.
2. In the target account, create the same additional fields — the same names, types, and lists.
3. Import the exported file and map each column to the corresponding field.

Create the fields before importing the contacts, so the values land in the right fields.

Workflows. Workflows cannot be copied or transferred between accounts — Copy to another account works for message templates only. Rebuild them in the target account manually. Opening the source and the target account side by side helps: move the blocks, then the start configuration, events, conditions, messages, and the exit conditions. See Building and Editing Workflows.

Account-level settings. These are configured from scratch and are not content:

• Infrastructure — domain verification, DKIM and SPF records, senders, and the short-link domain. The same sending domain can be added to several accounts only with the same verification type. For example, if the first account uses the Subdomain type, the second one has to use it too. Add the domain in the target account and publish the verification record generated for it. Don't change the existing records that the source account uses. If the domain refuses to verify, the usual cause is a different verification type or a different subdomain in the account that already holds it. See Setting Up Email Domain Authentication and Adding/Changing/Deleting a Sender Name.
• Access — users, roles, and API keys. See Managing Users.
• Data and automation — event types and segments.
• History — campaign statistics and message history stay in the source account.

Recommended Order

1. Verify the domain and add senders in the new account.
2. Create the additional field lists and fields.
3. Import contacts with their custom field values and check their subscription statuses.
4. Copy or re-create the message templates and check their settings and personalization.
5. Register event types and switch the integration over.
6. Build the segments, then the workflows.

Related Articles

• How to Migrate to Yespo from Other Platforms
• Managing Users
• Building and Editing Workflows
• Creating Additional Fields