Transferring Data and Content Between Accounts

Reteno has no single tool that transfers 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 Reteno from another marketing platform, see Migrating to Reteno.

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, without exporting files. It works for messages of all types.

Copy to another account is available to users of the parent account, and the destination account has to be a child of it — ask support to link the accounts if it isn't. Open the message list, use the copy action, and select the destination 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 destination 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, and external data sources: they reference the configuration of a specific account;
• personalization variables that read custom fields. Fields created in the destination account get their own identifiers, so any expression that addresses a field by ID has to be updated. See User Profile Variables and Velocity Features.
• that every image in the message still renders.

Copying the HTML Instead

If the source email was built as custom HTML, copy its code and create an HTML email in the destination account. This also works between unrelated accounts.

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 them into the new one. 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 Migrating to Reteno for the correct procedure.

Custom fields. There is no automatic copying of custom (additional) fields between accounts. List their names, types, and allowed values in the source account — on the Additional fields tab or with the Get additional fields API resource — then recreate them in the destination account.

The API resource returns field definitions only, not the values those fields hold for individual contacts. Create the fields before importing contacts, so the values land in the right fields.

Workflows. There is no self-service transfer of workflows between accounts — Copy to another account works for message templates only. Rebuild them in the destination account: move the blocks, then the start conditions, events, conditions, messages, and the exit conditions. Opening the source and destination accounts side by side helps: move the blocks, then the start configuration, events, conditions, messages, and the exit conditions. See Introduction to Workflows.

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

• Infrastructure — domain authentication and senders. 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 destination 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 a Sender.
• Access — users, roles, API keys, and SDK access keys. See User Management for parent and child accounts and who can copy templates between them.
• Data and automation — event types, segments, and tags. See Creating Events.
• History — campaign reports stay with the account that sent the campaigns.

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 and check their subscription statuses.
3. Copy or re-create the message templates and check their settings and personalization.
4. Recreate event types, then rebuild the segments and the workflows with their start conditions.
5. Run each workflow once for a single contact before activating it.