Exporting and importing objects between servers

The following information pertains to imports and exports:

• The source and target servers must have the same version of Unica Campaign installed.
• Regardless of whether you are exporting or importing a campaign, session, or flowchart, you must use -s to specify a .ses file. If a campaign or session includes multiple flowcharts, you can specify any of the associated .ses files.
• Before you can import a flowchart to a target system, the flowchart .ses file and its associated campaign or session must already exist on the target system. Therefore, you must: 1) manually copy the entire Campaign|partitions|partition[n] folder structure to the target system. You do not need to copy the tmp folder, and you may or may not want to copy the logs folder. Before you remove any files from the source system, be sure to do a complete backup of the entire folder structure (although you can omit the tmp folder). 2) Ensure that the .ses file for the flowchart exists on the target system (it should, if you copied the folder structure), and 3) Use unica_acsesutil to import the associated campaign or session to the target system. After you complete those steps, you can use unica_acsesutil to import each flowchart.
• When you do an import, the unica_acsesutil imports data (such as session info, triggers, or custom macros) into the system tables. During the import, it checks whether each object already exists on the target system. The check is done based on internal object ID. If the internal campaign ID is not unique, unica_acsesutil asks if the campaign should be overwritten. If you choose to overwrite the campaign, unica_acsesutil removes all data associated with the existing campaign on the target server, and then imports the new campaign. Similarly, when importing offers, unica_acsesutil checks the internal Offer ID for uniqueness. If an object with the same ID already exists, you have the option to skip that object in the import process or to replace the existing object.
  Note: If you know that an object (such as a campaign, session, or offer) already exists on the target system prior to import, consider deleting the object before you run the import, to avoid being prompted to resolve the conflict.
• If you plan to import Unica Deliver or Unica Collaborate flowcharts, that application must already be installed on the target system. If the application is not installed, unica_acsesutil generates an error and does not import the objects.

Moving objects between servers is done in several stages, with some manual steps required. A complete export and import is described below. You may choose to perform some subset of these steps.