Anyone who has ever gone through a large scale content migration project will agree that migration often equals migraine. Your vast collections of content that was originally created in DreamWeaver, then passed on to a custom Content Management System and finally to WordPress in 2009.
Now your business has grown so that you’ll need to integrate your site with your back end business systems. WordPress could accomplish this as could Drupal, but your organisation is already familiar with the Symfony 2 Framework, so you’ll look at options for embedding your content to that – without breaking link integrity, broken images, layouts, etc. headaches.
You could merge your WordPress application with your Symfony 2 business application with StackPHP or some PSR-7 implementation, but for stability and further integration you’ll move your content to eZ Platform. For this you’ll need to have a content migration project – which is not an easy feat.
Read more on Content Migration Projects and common pitfalls in them:
- WordPress, Drupal and eZ Publish Data and Content Migrations
- Content Migration: Lessons from Experts
- Integrations and Migrations at Exove
- IoT does not need Drupal if you’ve got a Graph Database