A first step in any migration is to clean up your entry data. That doesn’t change when moving from WordPress to ImpressCMS.
Cleaning up your content can be done in several ways : removing old or no longer relevant posts (news items get old soon, and Google doesnt like stale news items), looking into content types that perhaps no longer need to be on the new site, and cleanng up your tags and menu structures.
It depends mainly on your content, so it is difficult to automate this step. However, if done correctly at the beginning of a migration, this step can make the difference between success and failure in the end.
One of the big sayings in open source is to ‘eat your own dogfood’, meaning that you need to use the tools you develop also yourself on a daily basis.
It’s the only way you can get a good idea of the strengths and weaknesses of your solution, by putting you in the position of the end-user.
I have been a sinner in that regard, by using WordPress for my personal blog instead of my own project ImpressCMS. That is something I intend to set straight in the near future by migrating from WordPress to ImpressCMS, and documenting the process step by step.
After getting increasingly dissatisfied with the service from Codesion, ImpressCMS decided to switch to another provider. We had few requirements, and so we started searching for a solution based upon those:
- free or affordable for our budgets
We also thought of the possibility of doing the hosting ourselves, but that would mean an investment of time and effort, which would be unavailable for other tasks. Overall, we thought it was best to let specialized service providers handle that kind of non-core activity. Continue reading ImpressCMS Trac migration to Sourceforge