Migrate from Sitecore to Magnolia CMS
Sitecore is perhaps the most sophisticated .NET CMS in the world. It works for managing, testing, optimizing, personalizing, and automating content. So, large or content-centric companies whose work is complex and heavily dependent on content customization and personalization may like this software. However, other companies with a different model who acquire Sitecore may soon realize they had acquired a software too sophisticated for their needs. Considering the cost of licensing and management, they may have to migrate to a simpler, more affordable, yet highly effective software such as “Magnolia CMS“.
Magnolia Open Source CMS
Magnolia is an open source Content Management System tool completely written in Java. The Magnolia application has its features operating as modules. Features can be added or removed by installing or uninstalling modules. Magnolia comes in 3 editions, which are Community, Enterprise, and Enterprise Professional editions. The Community edition is the open source version of the software with multiple CMS features as modules. Additional modules are found in paid EE and EE Pro editions. Also, Magnolia offers services with its cloud-based platform.
Migrating from Sitecore to Magnolia
Magnolia is an open source, module based software with good documentation as well as a lot of community support. This makes it easier to use. Using Magnolia community edition, the migration can be done by developing modules that support desired specific features. These features can also be extended wherever required.
A little bit of experience in Magnolia will be of help here, as some of these challenges creating the individual modules may be encountered:
1. Developing a Magnolia content application to design HTML templates. Dynamically change the content using the responses from the client services.
2. The spring blossom module allows for integration with web services so that dynamic content can be displayed in the app.
3. Integration of Magnolia with the security system requires carefulness, to not expose the security system to hackers. Systems such as Active Directory and LDAP can be used to support Single Sign Ons for the application. Good documentation and community help is available to aid the developer in building a great module that enables authentication and authorization of users in the security management system.
4. Developing approval workflow is yet another challenge to face. With a workflow, the templates created by one user can be sent to his manager for approval. Then, the template goes live upon approval. The manager would also be able to request changes where needed. Where one is unable to use the 4-eye workflow module available only in the EE feature, a custom workflow module can be implemented to support 4-eye workflow feature.
Other features include images management, using external fields to control WYSIWYG editor options, creating XML editor to support universal web service and implementing the templates on multiple environments.
The developers at Charter Global specialize in open source implementation of the Magnolia application as part of their cost cutting strategy. With experts that record success working with various Open Source Content Management Systems such as Magnolia, Drupal, WordPress, Liferay and others, we are open to work in any technology our clients recommend.