The best way to migrate content from one system to another is to use an API. An API (Application Programming Interface) is a set of programming code that allows two applications to communicate with each other. It provides a way for developers to access data and functionality from an external source, without having to manually move the data between systems.
The process of migrating content using an API depends on the type of source and target systems, as well as the type of content being migrated. Generally speaking, the process involves creating an API request, which is sent to the source system, and then the source system responds with the data or content. This data is then processed by the target system and used to create the content in the target system.
In some cases, the source system may provide an API specifically designed for content migration. In other cases, the API may be a generic tool that can be used for content migration. In either case, the API must be configured correctly to ensure that the content is migrated successfully.
Once the API is configured, the content migration process can begin. The source system will send the data or content to the target system, and then the target system will process the data and create the content in the target system. Depending on the complexity.
Migration Architect is a highly configurable platform to conduct complex high-volume migrations and leverages the full functionality of source and target systems and their supporting APIs. If no API exists, then we can construct an access method that allows us to access the relevant content, structure, and metadata from the system in question.
T-Systems has delivered content migration projects for the following systems. The flexible nature of the migration platform enables connectors to be written for any system so in theory there is no restriction on the target system that can be loaded to with the T-Systems tooling.
SharePoint 2003, SharePoint 2007, SharePoint 2010, SharePoint 2013, M365, Teams
WCM, FileNet, Connections (now HCL), Quickr, SmartCloud, Notes, Domino, Content Manager, CM/OD
Day CQ4, CQ5, AEM