Transferring your team modules

When you've created your Design Studio team modules in the staging environment, it's possible for you to transfer them to production so you don't have to recreate them there. This is also useful if you have several Engage accounts and need to transfer team modules between them.

Tenants

A "tenant" is a dedicated Voyado Engage environment / account that contains all your customer data, configurations, campaigns, and integrations. Staging and production can be seen as different tenants, and if you work with multiple brands or business units, for example when you want to keep different environments apart, you are also working with different tenants. Tenants are isolated from each other.

Transferring modules between any two of your tenants works in the way described here.

Exporting a Team module

  1. Go to the Engage tenant you'd like to export from
  2. Open a template or sendout in Design studio
  3. Go to Team library and find the module you want to export
  4. Export the module (select this in the three-dot menu under the module)
  5. The module is now stored in the clipboard (memory)
  6. Continue with the import right away (see below)
The export will not transfer localized content, uploaded custom fonts, CSS or images from the image library. They need to be added to each tenant. You can only export one module at a time.

Import a Team module

When you have completed the export and have the module stored in the clipboard, you can continue with the import in the other Engage environment or tenant.

  1. Go to the Engage tenant you want to import to
  2. Open a template or sendout in Design studio
  3. Go to Team library and select import (select this in the three-dot menu at the top of the list)
  4. In some cases a dialogue will pop up to inform you that:
    • The module uses a saved Style that is not present in the current Engage tenant. You will be asked to import it as well.
    • The module you are about to import requires a data source. You will need to add the data source to the Engage tenant in order to use the module.  
  5. If needed, change the module name
  6. Click on Import. The module will now be in saved in your Team library
  7. Try the module in the canvas and render with data
    • If needed make adjustments, add localization or update data parameters and display conditions. 
    • After changes make sure to Update the module in team library
Styles are not synced between tenants. If a style has different style settings, the module will not look the same as where it was exported from. Instead, the style from the destination tenant will be applied.
Different tenants may not have the same data model, so parameters or display conditions may be missing when you transfer modules.
When using a target audience, labels or other object in a display condition, tenant data will not match as each tenant has its own IDs in the background. In this case these criteria will need to be updated.

Import updates to a Team module

You can update an imported Team module by following the same process as for export and import above. 

When updating a module the current module will be completely overwritten. It is not possible to undo this action. 
Synced modules cannot be updated, only added as new ones.

Designing for several Engage tenants

In case you are running several Engage tenants and would like to align the message design between them, we recommend that you decide one master tenant where design work is done and then transfer team modules to the other tenants.

  1. Design the module and save it in the Team library
  2. Export the module
  3. Switch to your other tenant
  4. Import the module. (Continue with same action if you have several tenants. The last exported module will stay in the clipboard.)

If needed, add the imported module to the canvas and make adjustments/localization to the module for the specific tenant and then update it in the Team library.

Was this article helpful?

/