Get more content like this

Planning an AEM Migration? Here’s a Roadmap for Your Success (Part 3)

AEM Migration, Adobe Experience Manager, AEM 6.1, TechAspect AEM Partnership
By

If your organization is planning to migrate to AEM, this three-part blog series provides a helpful overview of the process, including best practices and all the areas you should consider before you begin. This blog is the final post in our series. Read Part 1 and Part 2.

Today, we’re taking a look at the final three steps that should be considered early in the AEM migration process. Our hope is that this overview will give you more detail around the process itself, and better prepare your enterprise for an efficient and successful transition.

  1. Map out your integrations – You will need to define the various third-party integrations needed in the different pages, a high-level overview of the type and sections of content to be personalized, and the analytics data that needs to be captured. All of these play a significant role in how data is represented in AEM. During this phase, your team will need to consider the following:
    • What level of personalization do you want to provide?
    • What are the KPI’s and metrics?
    • What is the primary source of data for various content sections on each page?
    • What analytics can you capture out-of-the-box versus what needs to be developed?
    • What kind of e-commerce systems need to be involved (and what third-party interfaces do they provide)?
    • How do you want to accommodate and access user-generated content?

    In many implementations, these topics have come as afterthoughts, which required rebuilding of the application because the templates and components didn’t allow the right level of personalization demanded by marketing. Understanding the desired level of personalization up-front helps the development team create the applications necessary to support it.

  2. Define your administration process and hosting mechanisms (usually in conjunction with Adobe) – During AEM migration, your team will also need to consider the following:
    • Which hosting mechanisms are most appropriate for your needs? (AEM Managed Services, AEM in private cloud or in-house data centers.)
    • What are the different landscapes that you need (e.g., Dev, QA, stage, content, pre-production, production instances)?
    • What level of automation do you need to support testing and deployments?
    • How will you address continuous integration and deployments?
    • Capacity planning: How many CPUs do you need? How much of the content can be cached? How much of your website is based on queries and dynamic data?
    • What is your average traffic? How many hits do you receive?
    • How intense are your content authoring and workflow needs? (And what capacity does your system require to handle them?)
    • How do you plan to synchronize content between systems and how closely do you want systems to resemble each other?
    • What level of access controls are needed?
  3. Complete your content strategy and go live – Finally, your team will need to define your path to production for content. Specifically, you will need to consider:
    • How do you plan to address content translations and the relationship between the content in various locales? (What happens when a translation comes in, and what will be your process to make updates?)
    • Content strategy: What’s your plan for language- and country-specific content?
    • What localization mechanisms and tools are required? What level of support needs to be built in to the application to support these?
    • Searching: What is your general search strategy? What are the indexing needs of the system? Do you need separate instances? (All of this affects how the application is built.)
    • How will your various business processes map to workflows in AEM? (What are the different groups? Who are the approvers? How are the workflows defined?)
    • What’s the best way to facilitate migration? (Should you automatically migrate content from the old system or simply create new content in the new system? What various relays and redirects are needed in the new system when you go live?)

Do You Need Help Migrating to AEM?

If you are:

  • Evaluating AEM
  • Starting your migration and in the process of identifying the best approach
  • In the process of migrating to AEM and need a health check

Or if you are:

  • Needing to put your AEM migration is at risk, and you would like to put it back on track

We are here to help. 

If we find you to be a qualified customer, we will provide you two hours of consulting by one of our experts in AEM migration, free of charge. Contact us and start the request process now.

Need help powering your website with Adobe?

Get In Touch