How a Delta Migration Moves Content More Efficiently into AEM | AEM Community Blog Seeding

Avatar

Avatar
Establish
Community Manager
kautuk_sahni
Community Manager

Likes

1,200 likes

Total Posts

6,394 posts

Correct reply

1,147 solutions
Top badges earned
Establish
Coach
Originator
Contributor 2
Contributor
View profile

Avatar
Establish
Community Manager
kautuk_sahni
Community Manager

Likes

1,200 likes

Total Posts

6,394 posts

Correct reply

1,147 solutions
Top badges earned
Establish
Coach
Originator
Contributor 2
Contributor
View profile
kautuk_sahni
Community Manager

13-07-2021

BlogImage.jpg

How a Delta Migration Moves Content More Efficiently into AEM by Divya Kandikatti

Abstract

Moving from a legacy CMS into AEM requires the organization and management of a lot of moving parts; each of which must be rooted in your current needs, while keeping future strategic goals in mind. One of the most crucial steps is data migration, because the content needs to be moved into, and made acceptable, for the new system.

A complication often occurs because of the time gap between content migration completion and site launch, when a data clean up is necessary. However, for most organizations, authors are not likely to be able to stop creating content for any length of time. It is critical to define a content cutoff strategy to ensure that all of the content created in this interim is migrated over to the new system, yet allows the least interruption to modifying and generating new content.

Delta migration is a process that was created by Blue Acorn iCi experts in response to a recent client migration project to address the long duration of a typical content freeze. Using the Content Scanner tool, also developed in-house, our team created a way to minimize the burden on both the client’s authors, as well as our own consultants.

There are a few terms defined below that will help in understanding the concept and benefits of a delta migration.

Content freeze: The content freeze is the time period when authors cannot make any changes to content, including creating, updating, or deleting – within the legacy CMS or AEM system. It normally occurs after a migration, when the data must be cleaned.

Double posting: A double posting is when authors must post in both the legacy CMS and the AEM environment. In this case, content authors will be responsible for making sure the legacy and AEM systems are completely in sync with any changes they’ve made (ie creating, updating, or deleting content). It occurs during a migration when two systems are active (the legacy and the new AEM systems).

Read Full Blog

How a Delta Migration Moves Content More Efficiently into AEM

Q&A

Please use this thread to ask the related questions.