CMS migrations and upgrades

Old versions of systems lose support and become a security risk. I carry out upgrades to new versions and migrations between systems so that what matters is preserved: content, addresses and features.

Types of work

Upgrade to a new version

Moving to the current version of the same system, e.g. an older Drupal, WordPress or OJS. This often requires rebuilding the theme and replacing obsolete modules.

Migration between systems

Moving content and users from one CMS to another, e.g. from Drupal to WordPress.

Migration from a static site

Moving a hand-written site into a content management system.

Change of hosting and environment

Moving the site to a new server, a new PHP version and database.

How a migration works

  1. Audit – inventory of content, features, plugins/modules and URLs.
  2. Plan – scope, content and URL map, risks.
  3. Test copy – migration first, away from the live site.
  4. Verification – joint review of content and features.
  5. Launch – switch-over, 301 redirects, post-launch checks.

What we protect

  • Content and media
  • User accounts and permissions
  • URLs (301 redirects)
  • Search visibility

Open Journal Systems

OJS migrations are especially demanding. I have prepared a separate page for them.