WordPress to Plone migration
In case you are facing a big issue of dissatisfaction with your current WordPress website, why not to try more robust and secure Plone solution? The process of transferring all your data may seem difficult and risky, but with right methods you will only win from migration.
Website migration refers to moving web content, design, metadata and other elements from one platform to another. Each migration process is unique, especially when it concerns two so different CMS as WordPress and Plone. Usually migration requires an individual set of automated tools and collaborative efforts of human resources.
First and foremost, before migrating anything we must quantitatively and qualitatively assess your current web content. Special attention is paid to content types differences. While WordPress has 5 default post types (post, page, attachment, revision, navigation menu), Plone offers 8 standard content types (folder, page, event, news item, file, image, link, collection). And do not forget about custom content types available for both platforms. So it is necessary to choose content items transformations on initial stages of migration. To develop content strategy we will also need to gather information on:
- navigation/project/folder structure if it exists;
- relevant and out-dated (could be left behind) content;
- users, user authentication process, groups and their rights within WordPress;
- workflows and content validation;
- languages and translations if any;
- specific customizations and personalization additions implemented on the current WordPress website.
The next stage is focused on metadata strategy. Anything that will help website visitors to quickly find the information they need and make your content searchable, sortable, displayable, and easily accessible must be taken into account. Content mapping specifications are also very important and include rules for the mapping between old and new system.
Then we take care of the migration itself using technical solutions (e.g. automation, writing new code/script/program, etc.). As a rule, migration is performed to test instance, where website can be reviewed, validated and tested. Only after cleaning up and successful testing new Plone website can be moved to production environment.
Despite the popularity of WordPress, this CMS has a number of drawbacks, so eliminating them by migrating to Plone will cover most of your short- and long-term needs. For instance, WordPress websites lack security. Every time you decide to use new interesting plugin or free theme you allow access to admin dashboard. Moreover, WordPress runs on PHP and stores data in MYSQL database that opens possibility for SQL injection attacks. One of the ways out is custom security plugin, another - frequent WordPress update. The latter requires constant changes and updates to design templates: advanced theming and WP scripting are usually quite costly. On the contrary, Plone takes security very seriously.
Depending on the depth of the customizations required by the client, WordPress website specific customizations and various other features, migration process steps may differ. The result remains the same - successful migration to the new Plone-based website. Contact Quintagroup today to use our cost-effective and high quality Plone migration services.