This content originally appeared on DEV Community and was authored by Jeroen Fürst
Transitioning from Kentico Xperience 13 (KX13) to XbyK is a significant move that requires careful planning. While you might be satisfied with your current platform and are a fan of Kentico 😉, considering a migration now can help you make the transition more cost-effectively in the future. Think of it like maintaining your car 🚗—regular check-ups and part replacements keep it running smoothly. Similarly, modernizing or replacing components of your platform over time sets a solid foundation for the next generation.
Starting early allows your organization to strategize the best approach, and your agency or friendly neighbourhood Kentico Partner 🦸 can offer valuable guidance 🤝. There's no need to do everything at once; gradual preparation can make the process much smoother.
Key Considerations for a Successful Migration
Here are 10 essential steps to guide you through a smooth and efficient migration from Kentico Xperience 13 to Xperience by Kentico:
1. Understand that Migration is necessary 🛠️
An upgrade from KX13 to XbyK isn't possible due to significant technological changes. The biggest shift is the replacement of the CMS based on webforms with a modern, super-fast frontend technology—React ⚛️. This change means certain concepts and functionalities work differently in XbyK.
2. Evaluate the Kentico Roadmap 🗺️
Don't hesitate to get started—being informed puts you in control. By regularly checking roadmap.kentico.com, you'll stay up to date with upcoming features and monthly updates. This helps you plan your migration more effectively, especially with XbyK’s composable architecture. If certain functionalities can be replaced or updated within your current platform, it could make the transition smoother. Whenever possible, prioritize features already available in XbyK to streamline the process and ensure a seamless migration.
3. Prepare your MVC Application 🧰
Ensure your MVC application is running on modern .NET. If you're currently using .NET MVC 5, your first step should be migrating to .NET Core MVC. Since XbyK also uses .NET Core MVC, this will make your API easier to migrate.
4. Align your Frontend Stack 🖥️
Make sure your frontend stack is compatible with .NET Core MVC and React. While the CMS is based on React, your frontend doesn't have to be. However, adopting React could offer additional benefits. Examine your current frontend code to see how it can be migrated to XbyK. If you're still storing unstructured HTML/markup in the database, prioritize updating these before beginning the migration.
5. Utilize Standard Modules 🧩
Replace custom-made solutions with standard modules from KX13. For example, if you use a custom URL module, consider switching to Kentico's standard solution called content tree-based routing. This change will allow you to benefit immediately from XbyK's architectural setup.
6. Allocate Time for Content Migration ⏳
Since a direct upgrade isn't possible, use migration toolkits to transfer your content to XbyK. A great tool for this is the Kentico Migration Tool📦. An advantage of this approach is that necessary content models are created automatically. This method isn't limited to KX13; you can migrate from other platforms as well via the Universal Migration Tool. Using a universal format like JSON can expedite the process. Familiarize yourself with content modeling concepts in XbyK, such as the content hub and reusable content, to maximize benefits.
7. Leverage Page Builder and Widgets 🛠️
If you're already using the Page Builder and widgets, you'll be pleased to know they're compatible with XbyK. While KX13 widgets can be used in XbyK’s compatibility mode with minimal changes, you may want to explore the new UI Form Components for enhanced editing capabilities. The migration can be done smoothly using the Kentico Migration Tool, which helps convert the Page Builder JSON data structure to be compatible with the new components. Keep in mind that while widget properties may need some adjustments, the views and view models will require little to no rewriting, ensuring a seamless transition.
8. Clean up unused content and functionalities 🧹
Reducing the amount of content and unused functionalities before migration can save significant time. Now is an excellent opportunity to phase out or remove elements that are no longer necessary.
9. Modernize your .NET Code 🔄
Update old .NET code to modern standards. This includes not only MVC but also any functionalities using packages based on outdated development techniques.
10. Rethink your Infrastructure and Deployment ☁️
With XbyK's different structure, you no longer need two app services to host the application. Reflect on how you want to handle hosting in the future. Consider whether setting up infrastructure yourself is still the best use of your resources. Kentico SaaS could offer substantial benefits by handling much of the heavy lifting. With just a few clicks, you can have a complete environment ready, allowing you to focus on developing your application.
Final Thoughts 💡
By starting preparations now, you can make the migration to XbyK a smoother and more cost-effective process. Regularly updating and modernizing components of your platform ensures you're ready for future advancements, such as expanding into other channels or leveraging AI 🤖. Kentico remains an excellent choice for organizations aiming to achieve digital growth without the need for complete replatforming. Reach out to your agency or Kentico Partner for advice tailored to your specific needs—they're there to help you navigate this significant transition.
This content originally appeared on DEV Community and was authored by Jeroen Fürst
Jeroen Fürst | Sciencx (2024-09-26T13:27:47+00:00) Tips for Migrating from KX13 to Xperience by Kentico. Retrieved from https://www.scien.cx/2024/09/26/tips-for-migrating-from-kx13-to-xperience-by-kentico/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.