Importing metadata

To import metadata into a Marketing Operations system, you select a previously exported archive file.

The import process validates the archive and its component files: the source and target systems must have the same version of Marketing Operations installed, and all files must be correctly formatted.

Marketing Operations data structures are interrelated. Duplicating the data structures of a source system is an iterative process: you import archive files, perform manual configuration, and potentially reimport archive files.

When you have metadata of more than one type to import, this sequence is the most efficient.

1. Marketing object types

   Import marketing object types first to assure that when you import templates, any templates for those marketing object types are also imported.

2. Project health rules
3. Templates
   • The global security policy for the target system is assigned to any templates that have a security policy that is not present on the target system.
   • Templates with defined rules that involve users who are not present in the target system are not imported.
   • Templates with defined rules that involve teams that are not present in the target system are imported, but do not function.

   Continue by importing security policies and teams, and then either import the template archive again or make updates to the target system as needed.

4. Security policies

   User visibility definitions for teams and user groups that are not present on the target system are not imported. Continue by importing teams, and then either import the security policies again or make updates to the target system as needed.

5. Teams

   After you import teams, review and update rules and user visibility definitions as needed.

After you import a metadata archive, be sure to review the results in the target system. Configure users, rules, teams, user groups, security policies, and templates as needed to integrate new structures into the target system.