Migration

Purpose.

To facilitate the migration of a campaign, session or flowchart from one environment to another. Migration option is only available for Campaign.

  1. In the left navigation pane of the HCL Unica Director, click Migration.
  2. In the Campaigns or Sessions tabs, you can select a campaign or session from the complete listing of all campaigns or sessions under the respective Campaign listing or Sessions listing sections.
  3. You can select the campaign or session from Folders list. After selecting a folder the Campaign Listings or Session Listings sections will be populated.
  4. Select the campaign or session that you wish to migrate.
  5. Select the Target environment. The Migration Marketing Platform url is auto-populated.
  6. Enter the Unica Platform user and Unica Platform password and click Authenticate.
  7. When authenticated, select the policy listed under Select policy of target environment
  8. Select the correct owner under Select owner of target environment.
  9. Chose the appropriate option If objects with same id on target environment then migration will
  10. Click Migrate.

Important Note:

Make sure to select and migrate a campaign or session first, only then flowcharts of these campaigns / sessions can be migrated. A user can also migrate more than one flowchart at a time by selecting multiple flowcharts.

Status of migration can be seen under Job queue.

Managing duplicate objects

Managing duplicate objects, (occurs when there is an ID conflict) requires one of the following options to be selected. (if there is an ID conflict):

  1. abort – Migration will be aborted when a duplicate object is encountered
  2. replace – The object being migrated will replace the duplicate object on the destination system.
  3. skip – The object on the destination system will be retained and the migration of the object on the source system will be skipped.

The migration imports data (such as campaigns, flowcharts, session info, triggers, custom macros, etc.) into the system tables. During the import, the migration process checks the pre-existence of each on the target system. The process checks the objects internal campaign ID for uniqueness. If it is not unique then the object gets replaced. If you choose to replace the campaign, it removes all data associated with the existing campaign on the target server, and then imports the new campaign.

If you know that an object, such as a campaign, session or offer, already exists on the target system prior to migration, you should consider deleting the object before you run the migration, to avoid any conflict in migrated object.

Be very sure before selecting Replace option:

If you select "Replace" option, the migration would replace all the identical objects it detects. It is strongly recommended that you review existing objects before using the "Replace" option as it would remove all references to existing Campaign / Session / Flowchart and replace them per the newly imported objects.

While selecting replace option, you should ensure that the selected object does not exist on the target environment, otherwise it will be replaced and all the other objects (e.g. Flowcharts) will be then associated with the migrated object.

For example: There is a Campaign on target system with ID = 6 and it has three flowcharts associated with it. If a user migrates a campaign whose ID is same as of target Environment i.e. 6 and selects the replace option, then after migration the newly migrated campaign will have three flowcharts associated with it which were not in the source environment.

Migration of campaigns / flowcharts

Note:

  1. HCL Unica Director does not support migration of campaigns / flowcharts when Plan and Campaign are integrated. You can utilize migration of Sessions and Session flowcharts with this integration enabled. Users will get Error "Campaign List : Invalid input provided for the API" when they click on "Campaign project" from Migration page. This error can be ignored as we do not support migration of Campaigns when plan and Campaign integration is ON.
  2. Flowchart does not get migrated if the Campaign / session name is renamed and flowchart is not edited / saved after renaming. The workaround is that the user must open a flowchart and save it so that the .ses file name is updated as well.
  3. When "web access control" login method is configured with Unica Platform, Increase the value for "Token Lifetime" setting from "Affinium|Manager|miscellaneous" of Platform to any value more than 15 sec , for eg: 9999 , to make migration work in HCL Unica Director.
  4. The same user data source’s with exactly same name as of Source Campaign Environment should be configured in the target Campaign environment as well, otherwise the table mapping of migrated flowchart will not work and all the process boxes will appear unconfigured.
  5. Unica Director uses campaign utility unica_acsesutil for migration , in case any error occurred while migrating using Unica director , user can check unica_acsesutil.log for more information at <Campaign_home>/logs/unica_acsesutil.log
Note: Migration of Journey is not supported.