A Seamless Migration: Transitioning from Your Old CMS to Zesty
Migrating an enterprise website to a new Content Management System (CMS) is a multifaceted endeavor that demands meticulous planning and execution. In this comprehensive guide, we will delve into the intricate stages of this process, from the initial Discovery phase to the ongoing post-launch Implementation. Each step plays a critical role in ensuring a seamless transition and optimal performance of your digital presence.
Definitions:
Zesty: The Zesty company
Customer: The Subscriber to a Zesty license
Implementer: This is the individual or group who configures the schematics and templating within the Zesty platform. The implementer can be an ODD, Agency, and/or Customer internal developer.
ODD: On Demand Developer program from Zesty. These are individuals leased to the Customer from Zesty.
Agency: 3rd party agency hired by the Customer but is not associated with Zesty.
Phase | Responsibility | Resource | Notes |
Zesty | Zesty Management | ||
Customer | Customer | The customer will be responsible for overseeing and project managing the overall migration and implementation. | |
Zesty | Zesty Management | ||
Zesty | Zesty Engineers | ||
Zesty | Zesty Support | The resource who gets trained is the developer or agency who will be implementing | |
Customer | Implementer | The implementation can simultaneously occur with migration | |
Customer | Implementer | The implementer will be responsible for training the end user | |
Customer | Implementer | ||
Customer with help of Zesty | Implementer | ||
Customer | Implementer |
Discovery:
In the discovery phase, the project team assesses the current website and identifies the reasons for the CMS migration.
Goals and objectives for the migration are defined.
Stakeholder needs and requirements are gathered, and any potential challenges or risks are identified.
The owner of the migration script will need access to all code repositories.
Access to the existing CMS will be granted to the migration script owner.
Any necessary third-party integrations are documented.
Project Plan:
A comprehensive project plan is developed, outlining the scope, timeline, budget, and resources required for the migration.
Roles and responsibilities of team members are defined.
Key milestones and deliverables are established to keep the project on track.
Migration Planning:
Detailed planning is done for the migration process, including data migration, content mapping, and URL structure.
Migration strategy and approach are determined, taking into account SEO considerations and minimizing downtime.
Migration:
Actual migration of content, data, and assets from the old CMS to the new one takes place.
Data integrity and consistency are ensured during the transfer.
The new CMS is configured to meet the specific needs and requirements identified during the discovery phase.
Data is imported and structured in the new CMS.
Developer Training:
Developers and IT staff are trained on the new CMS platform to ensure they can effectively work with and support the new system.
Training may cover CMS customization, template development, and troubleshooting.
Implementation:
Additional CMS configurations are set as needed after the content migration.
Templates, themes, and 3rd party plugins are installed and customized.
URL redirects are set up to maintain SEO rankings and user experience.
Design frameworks are installed, developed or migrated.
Javascript frameworks are installed, developed, or migrated.
Responsiveness is implemented to accommodate device widths.
Form submissions are connected to Customer’s CRM system.
Auditing of SEO, broken links, missing content, and functionality is handled on an ongoing basis.
All content items, code, and additional files are published in preparation for launch.
End User Training:
Training sessions are conducted for content creators and administrators who will use the new CMS.
Topics covered may include content creation, publishing, workflow management, and user access control.
Testing & QA:
Rigorous testing is performed to identify and address any issues or bugs in the new CMS.
This includes functional testing, usability testing, and performance testing.
Quality assurance checks ensure that the website functions correctly and meets the established criteria.
Launch:
After successful testing and approval, the new CMS is launched to the public.
DNS settings are updated, and the website is made live.
Monitoring tools are put in place as needed to track the website's performance post-launch.
Ongoing Implementation:
Post-launch, ongoing support and maintenance are crucial.
Regular updates, security patches, and content updates are part of the ongoing process.
Any net-new designs or development can continue after launch with the customer’s resources.
Common Terms:
URL redirects: The process of creating rules that automatically forward website visitors from old URLs to new ones, typically used during CMS migration to maintain SEO rankings and user experience.
Data integrity: Ensuring the accuracy and consistency of data during the migration process, so that information remains reliable and error-free.
Customization: Tailoring the CMS to meet specific needs and requirements, often involving the development of unique features or functionalities.
SEO (Search Engine Optimization) considerations: Factors and strategies implemented to improve a website's visibility on search engines, ensuring that the website ranks higher in search results.
Audit (in the context of SEO): A systematic examination of a website's content, links, and technical aspects to identify issues like broken links, missing content, and other areas that require improvement.
DNS (Domain Name System) settings: The configuration that associates domain names (e.g., www.example.com) with the corresponding IP addresses, enabling users to access websites using human-readable names.
Net-new designs: Refers to entirely new design concepts or elements that may be introduced to a website after the migration process, typically with the aim of enhancing visual appeal or user experience.
Security patches: Updates or fixes applied to the CMS to address vulnerabilities and protect the website from potential security threats.
Monitoring tools: Software or services used to track website performance, including metrics like site traffic, load times, and error rates, post-launch.
Content Management System (CMS): A software platform that allows users to create, manage, and publish digital content on a website.
Stakeholder needs and requirements: The specific demands and expectations of individuals or groups with an interest in the CMS migration project, including clients, users, or other relevant parties.
Migration script owner: The individual or team responsible for overseeing and executing the code and processes required for data migration during the CMS migration project.
Template development: The process of creating pre-designed layouts or templates for web pages within the CMS to ensure consistent styling and structure.
Workflow management: The coordination and automation of content creation, approval, and publication processes within the CMS to streamline content production.
Quality assurance (QA): A systematic process of ensuring that the website functions correctly, meets established criteria, and is free of defects or issues.
Responsiveness: The design and development approach that allows a website to adapt and display optimally on various device widths, such as desktops, tablets, and mobile phones.
Form submissions: Data entered by users in online forms on the website, which may need to be connected to the organization's Customer Relationship Management (CRM) system for effective management and follow-up.
By Gisele Blair
A designer knows he has achieved perfection not when there is nothing left to add, but when there is nothing left to take away.