1.
SAMPLE 1: Site Migrator documentation
Working with Site Migrator
Ingeniux CMS 9.0 SR1 includes the Site Migrator utility, a tool that packages site content and
imports packaged content while preserving hierarchical page
relationships, presentations, schemas, and taxonomy information. Site Migrator can migrate
branches of a CMS site, and it's especially useful for archiving content like outdated news articles
or blog posts.
To access Site Migrator, navigate to Apps > Site Migrator.
The migrator has two main areas:
• Package: Bundle a branch of a site.
• Expand: Import a package.

2.
Packaging(a(Site( (
On Site Migrator's Package tab, you can select a branch of a site and convert it to a
deliveriable, serialized format.
To select a site branch, enter or drag its xID to the Drag in pages to be packed field. The
package consists of this page and its child pages. In the next field, enter a name for the
package.
After selecting the site branch and naming it, there are several options to consider:
• Preserve categorization for pages: When enabled, includes the pages' taxonomy
information (in the form of the taxonomy tree XML file) in the package.
• Package associated categories: When enabled, packages a site's full taxonomy tree.
• As Archive: When enabled, deletes the selected page and its descendants after the
package has been created. As the name implies, this option is useful when archiving
sections of a site.
• Integrity check: Checks whether the site node about to be packaged is self-contained. If
the package contains any references to xIDs outside the node (links, navigation start
pages, component references), a list of these xIDs appears in the Status area.

3.
If the package contains missing xIDs, you can still proceed with it. Note, however, that
the pages may contain broken references when imported to a new site.
When you're ready to package the selected pages, click Package. The resulting package is
stored at [siteName]App_DataxmlCustomSiteMigrator9packages[packageName]. Its
structure looks as follows:
• files: The XML file for each page in the package.
o presentations: Any page presentations and content units associated with the
packaged pages.
• Schemas: The XML schemas associated with pages in the package.
• Stylesheets: The style sheets associated with pages in the package. This includes style
sheets for page presentations.
• tree.xml: The site tree for the packaged pages, which defines the relationships between
them.
• TaxonomyTree.xml: The taxonomy tree for the packaged pages. Only included
when Preserve categorization for pages is enabled.
Expanding(a(Site(Package(
On Site Migrator's Expand tab, you can import a packaged branch of a site to a selected site
node.
Click the arrow in the Pick a package field and select a package from the list that
appears. Click Check Package to view the package's content as it would appear in the site
tree.

4.
Next, drag the page under which the packaged pages will be located to the Drag in the
page... field, or enter the page's xID in this field.
There are several options for package expansion:
• Apply page categorization with matching category IDs:
• Create categories from package: When enabled, uses the packaged taxonomy tree to
create categories for packaged pages.
• Keep original page IDs: When enabled, maintains the original xIDs of the pages in the
expanded package. If any xID in the package already exists in the site where the package
will be expanded, this feature doesn't work.
It's also important to note that, after using this feature, new pages in the site must begin
at an xID higher than any xID in the package. For example, consider a site whose highest
page is x567. After expanding a package whose highest xID is x1000, with Keep original
page IDs enabled, the next page, component, or folder created in the site will have the
xID of x1001.
• Define Schema Mapping: Clicking this button opens a dialog where you can configure
how schemas contained in the package correspond to schemas in the target site.

5.
To map a package schema to a site schema, drag a site schema from the righthand column to a
package schema on the left.
Clicking Map Same Names matches package schemas with any site schemas that have the
same name. After dragging a target site schema to an original schema, the schema opens. Here,
you can map the schema's fields in the same way you mapped the schema.

6.
To save a draft of the schema mappings, click Save Mapping Temporarily. When you're
finished, click Save Mapping and Close. Unless all schemas and schema fields have
been mapped, clicking Save Mapping and Close displays an error message.
When you're ready to expand the package, click Expand the package. You can monitor its
progress in the package area. When the expansion is complete, click Download the page ID
mapping log to download a CSV file of page mappings.

7.
Refresh your browser to view the expanded package in the site tree.