I migrated several huge CMSes in Financial Services and know you pain. Here is what I did and I hope you can use it. 2 things: - knowledge about the structure

I migrated several huge CMSes in Financial Services and know you pain. Here is what I did and I hope you can use it. 2 things: - knowledge about the structure - math, math, math You will need both exercises later on for the other CMS as well. Do the math: how many changes over time? Which department/person needs to do changes and why? Which files and content is affected? Prioritise: if there is no live actualization needed, postpone certain changes. Is there critical content? Do you need a workflow for certain changes (legal approval etc.)? You might need to mix different approaches: - using some scripts - using a deployment pipeline - using a lightweight CMS for parts of the content - using a dev team who does the changes manually (speed and costs do usually not warrant hacking a CMS for 6 month, so manual changes can be sufficient) For some frequently changed pages it can make sense, to have some sort of mini CMS or even simply have a small team of business and dev people who do the changes manually. Do not overengineer at this point, since this can lead to a fragile solution which backfires: "Why do we need the new CMS? It works currently." Have fun! :)