Today’s organizations fancy digital experience platforms as they reduce cost, increase efficiency, and improve customer experience for better return of investments. But migrating content and digital assets into a new customer experience can be a significant effort. Read our blog on typical enterprise needs that mandate migration from existing legacy systems to evaluate if you need to choose migration or not. As digital content management technologies mature, a successful and proven migration methodology is key in determining the suitability of one vendor’s product over another. But before you go about charting a migration strategy or choosing a methodology, bear in mind the following pre-requisites:
Redefine customer experience
- Conduct workshops to capture user requirements and related user experiences in terms of personas and journeys.
- Agree on project scope and limitations based on the standard parameters of time, function, and cost. Capture the same in the business requirements document.
- Prepare wireframes for the new user experiences aligning with the base structure of the source system content.
Understand source system
For successful migration you must have a very clear understanding of what needs to be migrated.
- Identify the domains/websites in scope for migration
- Analyze each domain for its pages, assets, metadata, and functionalities. Create a document to list all the pages, assets, metadata, and functionalities under each domain that needs to be migrated.
- Classify pages to break down large volumes of HTML structured or unstructured pages into a number of common areas or templates
- Prepare information architecture for each domain/website
Design target system
Once you define the source definitions, match these with the target environment. Some of the key points to consider while designing target systems are:
- Agree on the domain list that needs to be implemented in the target system
- Define the structure of the target information architecture retaining all the essential content of the source system
- Create templates in the target digital content management system aligning with the new user experience layouts
- Agree on the metadata requirement for the target system
Once you have defined both the source and target systems, the next step is to design the content transformation rules. The rules must address all aspects of the target system such as mapping configuration of the content to the template. The target system requirements always drive the definition and design of the rules from the target to the source system. The source system cannot always supply relevant data to populate the target system correctly. Incorporate an exception handling formula that addresses these instances of inappropriate source data or incomplete auto-generation. Ensure you fully define and test all transformation rules prior to coding. Each rule should have an associated exception and correction document. This document determines the test verification criteria, the identified exception, and the required corrective action.
How to define transformation rules?
- Cross match source pages to target pages for the exception and correction
- Cross match source classification to target templates and create a document that will have guide lines for the mapping of source system to target system
- Cross match any domain name changes
- Cross match granularity components. Document which “slots” migrate and which do not.
Once you have gathered the customer requirements and defined the customer experience, understand the source system and design the target system. Then, identify the transformation rules. Now you are all set to define the migration strategy and subsequently execute the actual migration of content. More about that in my next blog post.
Our Adobe experts will be present at the Adobe Summit, March 25-29, 2018, Las Vegas. Plan your meetings with our business and technology leaders and learn more about TCS’ successes in digital content and experience management and how we are transforming global companies with improved digital customer experience.