White Papers

Automate Content Transformation & Migration with the Power of AI

A Special Report for Adobe Experience Manager Customers

Executive summary

Organizations are looking to adopt Adobe Experience Manager (AEM) to reduce costs, increase efficiency, and improve content management flexibility, but migrating content and digital assets into a new CMS can be a significant effort.

Too often organizations begin a migration without fully understanding the challenges they face — resulting in slipped deadlines, reduced scope, and even project failure.

This white paper will outline the key challenges Oproma has encountered with multiple successful migrations to AEM and show how the MiCore Suite, leveraging Artificial Intelligence (AI) has addressed these challenges.

Key challenges

Component oriented publishing – A double-edged sword

AEM’s concept of Component-based content authoring enables users to build out compelling web content with a few screen taps. This focus on highly usable authoring succeeds where so many other solutions have failed; it places control of content firmly in the hands of the people writing that content.

Unfortunately, getting to the right answer often comes at the cost of having had to make compromises along the way. AEM customers often find themselves saddled with large volumes of content in legacy systems from a variety of vendors, or even old in-house solutions.

Moving non-component content into the component model can seem like an insurmountable task. For many, the cost of decomposing their legacy content into AEM components can take as much effort as rewriting the content from scratch.

Time and complexity

As migrations are tied around a timeframe, a lack of experience can easily lead project managers to underestimate this dimension. There are typically two sets of timeframes; one is for setting everything in place technically to start the migration, and the other is the start date of the migration. The time required for a manual migration vs. automated migration will differ greatly especially when complex pages are in play.

Manual Migration vs Automated Migration


Time consuming
Approx. 2-3 pages per hour.
Approx. 40 days for 1000 pages.
(Single resource)

Error prone due to manual human intervention. Link remapping and meta data


Approx. 5000 pages per hour.
(Single resource)

Once transformation/business rules have been tested, the process is fully automated.

Content and assets – Oh my!

In almost all cases, the customer is not fully aware of the quantity or quality of the content for their website. The content does not just consist of the text and images, it also contains links, other digital assets (video, PDFs, documents, etc.), custom styles, metadata, forms and permissions.

Another potential challenge in identifying and tagging content that is outdated, duplicate, no longer pertinent or simply you didn’t know existed.

So, what’s the problem?

As the Internet has matured, the age of the cowboy web developer is coming to an end. Those who are building robust, standards-compliant solutions still have to deal with the content in the systems created by those early innovators.

Legacy content was generally built for how it looked, rather than what it meant, and teasing the meaning out of old pages is time consuming.

MiCore solution

Identify – Perform an in-depth analysis of the website using MiCore Cataloguer which will generate a detailed content inventory listing every single page, asset (image, video, etc.) with a fully-indexed copy of the all content from the website. Using built-in Artificial Intelligence, content can be automatically classified using neural network training algorithms.

Understand – Use the content inventory (catalogue) to view analytics using MiCore Analyst to extract pertinent information relating to the number to pages, the number of assets, the size of the assets and the complexity of the pages within the site. This information is critical to the customer and to the vendor to make informed decisions before developing a migration plan.

Review/Evaluate/Plan – Determine which content and assets should be transformed, archived or deleted. Develop concrete business rules to ensure content is migrated accurately to proper destination.

Transform – The migration process itself involves the gathering of content and assets, the migration of assets (PDFs, videos, images, archive files, etc.) to the Digital Asset Management (DAM) and transforming the content pages and structure into AEM components (either custom or out of the box). This process also handles the remapping of all of the links from the original content to their location within AEM. This migration process is not only rapid, but also repeatable, ensuring that any required changes, either to components or content, occurring during a migration can performed and the migration itself can be repeated if necessary, without any intensive manual effort.

Verification – The final step of the process is to validate the content in AEM to ensure the content is accurate and has been migrated to the proper location.

Have questions for our team?