Content migration

Content Migration from external sources or from other TERMINALFOUR instances can be messy but it doesn't need to be. With Packages, you can gather assets and content together in a single file that can be imported to the same or a different instance.

There are two types of Packages:

1. External content Packages
2. Cross-instance Packages

External content Packages

These are the Packages that are used to migrate content from an external source into TERMINALFOUR. Before you use these Packages you should consider the following about the type and amount of data you want to migrate:

Database Content

If the content is in a database, then consider the External Content Syncer. This is great for text-based content that doesn't require a hierarchy or folder structure on import (e.g., staff profiles, program information etc.).

Have a look at this primer of content syncing to help you get started. Content Syncing is not ideal for HTML content because it won't import images or files (like documents) that are referenced. Neither will it parse for links and update them into TERMINALFOUR-managed links.

Manual vs auto-migration

Whether migration is auto or manual is down to the number and consistency of the page design. When all or most pages in a site adhere to a uniform mark-up structure, mapping to Content Types is straightforward and the auto-migration task requires less manual input. In most cases, a combination of manual and auto-migration is used to balance accuracy and speed. 

Talk to your account manager about the best way for you

The following Package types are used to migrate external content into TERMINALFOUR:

• Media Archive Package
  • used to bulk upload media files like images or documents to the Media Library.
• HTML Package
  • uses the DOM structure of the HTML page to determine the Site Structure, content area of the page, and the Content Type to be used for the content. On import, all documents and images that are referenced are imported into the Media Library, and any internal links between the HTML files are converted into TERMINALFOUR Section Links.

Cross-instance Packages

We've noticed some challenges with Packages in Terminalfour, particularly with complex builds which can cause problems during package creation and import. Specifically, creating channel and section packages can sometimes lead to corrupt packages due to the build or configuration within the application.

Packages was originally designed for less complex Terminalfour implementations and may not fully support more intricate features like programmable layouts and some navigation objects.

Your feedback is valuable to us! If you've encountered issues or have unique use cases for Packages, please reach out and share your thoughts and experiences with us. It helps us plan for future improvements.

The following Package types are used to export from one instance of Terminalfour to import into another instance of Terminalfour:

• Channel Package
  • exports the Channel configuration, Site Structure, Content, Media Items, and all assets that are used or referenced (Page Layouts, Content Types, Navigation Objects, Lists and Sublists) within a selected Channel. Once created, the Package can be imported into the Site Structure of the same or another TERMINALFOUR instance.
• Section Package
  • exports the Subsections, Content, Media Items, and all assets that are used or referenced (Page Layouts, Content Types, Navigation Objects, Lists and Sublists) within a selected Branch. Once created, the Package can be imported into the Site Structure of the same or another TERMINALFOUR instance.
• Group Package
  • export assets (Page Layouts, Content Types, Navigation Objects, Lists and Sublists) owned by a specific Group. These assets can then be imported into an existing or a new Group.
• Media Category Package
  • exports a Media Category, including Subcategories, and all Media Items from the Media Library. These can then be imported into a separate area of the same Media Library, or into the Media Library in a different TERMINALFOUR instance.
• Individual Assets Package
  • exports one or more specified Content Items, Content Types, Page Layouts, Navigation Objects, Media Items, Lists or Sub Lists