Transfer business rules
The transfer (export, then import) of content is subject to a number of rules and constraints.
- BluePrint hierarchy transfer constraints
You can export data Publication by Publication, then import them one at a time, and preserve BluePrint relations in that way. But there are some constraints about the order of these transfers, and about rearranging Publications in the hierarchy through a transfer. - Transfer behavior for BluePrint items
The BluePrint status of an item (localized, shared or local), as well as the configuration of BluePrint transfer behavior, affects its transfer. This topic explains the business rules for the transfer of BluePrint items. - Transfer mapping
During export, a file called mappings.xml is created that contains the implicit mappings in a mapping table. You can change these mappings in two ways in order to rename and/or move the items you are importing. Note that you cannot create new items or locations in this way. - Exporting content from SDL Tridion Sites 9 and importing it into SDL Tridion 2013 SP1 HR1
You can export content from SDL Tridion Sites 9 and import it into SDL Tridion 2013 SP1 HR1 using the Import and Export service in both Content Manager instances. Only a few restrictions apply: one, Business Process Type will fail to transport, because this item type did not exist yet in SDL Tridion 2013 SP1 HR1; and two, any Publication you export must have its Publication URL field set in its General tab. - Exporting content for import into a Content Manager instance older than SDL Tridion 2013 SP1 HR1
Because the Import and Export service is only part of the SDL Tridion Sites (formerly SDL Tridion) core as of SDL Tridion 2013 SP1 HR1, you cannot perform a complete transfer to a Content Manager instance older than SDL Tridion 2013 SP1 HR1 using only the Import and Export service. You can, however, perform an export using the service, and perform an import using Content Porter. - Transfer of selected items vs transfer of dependencies
In addition to items that are explicitly selected for export, an export may also include items on which that item depends: its dependencies. For example, a Component depends on a Schema, so if a Component is selected for export, then by default, its Schema is also exported. However, the import behavior for explicitly selected items is different than for dependencies. - BluePrint hierarchy transfer constraints
You can export data Publication by Publication, then import them one at a time, and preserve BluePrint relations in that way. But there are some constraints about the order of these transfers, and about rearranging Publications in the hierarchy through a transfer. - Transfer behavior for BluePrint items
The BluePrint status of an item (localized, shared or local), as well as the configuration of BluePrint transfer behavior, affects its transfer. This topic explains the business rules for the transfer of BluePrint items. - Transfer mapping
During export, a file called mappings.xml is created that contains the implicit mappings in a mapping table. Before import, you can edit this file to change these mappings, in order to rename and/or move the items you are importing. Note that you cannot create new items or locations in this way. - Transfer of selected items vs transfer of dependencies
In addition to items that are explicitly selected for export, an export may also include items on which that item depends: its dependencies. For example, a Component depends on a Schema, so if a Component is selected for export, then by default, its Schema is also exported. However, the import behavior for explicitly selected items is different than for dependencies.