User Guide

Transferring Content Between Accounts

What can and can't be moved when you set up a new Reteno account.

When you open a second account — for a new brand, a separate region, or a split of an existing project — only part of the setup can be carried over. This article lists what moves and what has to be built again.

📘

Note

This article covers moving content between two Reteno accounts. If you are switching to Reteno from another marketing platform, see Migrating to Reteno.

What You Can Transfer

Email Templates

Email templates can be moved in two ways:

  • Copy to another account. Available to users of the parent account, for message templates. Open the message list, use the copy action, and select the destination account.
  • Copy the HTML. Export or copy the message HTML from the source account and paste it into a new message in the destination account. This works between unrelated accounts as well.

After the copy, check the message in the destination account: senders, subscription categories, links, and personalization variables refer to objects of the source account and may need to be reselected.

Custom Fields

Custom (additional) fields can be reproduced in the new account:

  1. List the field names, types, and allowed values in the source account — in the Additional fields tab or with the Get additional fields API resource.
  2. Recreate them in the destination account, either manually or by importing a small file with one column per field so the fields are created automatically.

Use placeholder data for such an import rather than real customer data. Field definitions remain in the account after you delete the placeholder contact.

Contacts

Contacts are moved by exporting them from the source account and importing them into the new one. Create the custom fields in the destination account before the import, so the values land in the right fields.

What Is Not Transferred

The following is configured again in the new account:

  • Workflows. There is no self-service transfer of workflows between accounts. Rebuild them in the destination account. A transfer can be requested from [email protected], but it is a manual action and is not guaranteed.
  • Domain and sender settings. Domain authentication and senders are per-account. Repeat the setup in the new account — see Setting Up Email Domain Authentication and Adding a Sender. If you use the same sender domain in several accounts, the authentication configuration, including the technical subdomain, must be identical in all of them.
  • Event types. Event types and their parameters are created again in the destination account. See Creating Events.
  • Segments, tags, and reports. Segment definitions are rebuilt manually; historical statistics stay with the account where the sends happened.
  • API keys and SDK access keys. Generate new ones in the new account and update them in your integrations.

Planning the Move

  1. Set up the domain, senders, and access keys in the new account first — they gate everything else.
  2. Recreate custom fields, then import contacts, so the field values land in the right places.
  3. Copy the email templates and reselect senders and subscription categories in each.
  4. Recreate event types, then rebuild the workflows and their start conditions.
  5. Run each workflow once for a single contact before activating it.

Related Articles

Updated about 1 hour ago

Did this page help you?