Website modernization and migrations
Bringing an old site or system up to date: read it first, keep it safe during the work, then upgrade or move it with a rehearsal and a launch week you chose.
What you get
- An old system read end to end before anyone proposes a rebuild.
- A launch week you chose, after a rehearsal on a copy.
- Old addresses that still get visits redirected, so bookmarks keep working.
Where it goes wrong
A website migration starts from what works. An old site usually still does one or two things well, and those are the pages people bookmarked or linked from old emails. A migration that changes every address breaks them. A migration that moves every page moves ten years of outdated content into a new design.
A legacy system adds its own risk. The site runs on a version that no longer gets security fixes, such as Drupal 7 or an old release of PHP. Custom code written years ago holds a rule nobody wrote down, such as who gets the member price or when a registration closes. The membership database, the payment processor, and the mail list are wired into it, so nobody wants to touch it, and it falls further behind every year.
What we do
- An inventory of pages, files, and records, with a decision for each group: move, rewrite, archive, or delete.
- A redirect from every old address that still gets visits.
- A rehearsal import on a copy of the new site, with counts checked against the old one.
- For membership data, a plan for statuses, renewal dates, logins, and stored payments.
How we handle a legacy system
- Read it before proposing anything: the code, the database, the server, and every connection to another system. Each custom part gets a line in writing that says what it does and whether anyone still uses it.
- Make it safe while the work happens. If the old site has to stay up for months, we patch what can be patched, close what is exposed, and move the backups off the server. Server administration describes that work.
- Upgrade in place when the platform is sound and only out of date. Rebuild when the platform is the problem. The scope says which, and why.
- Keep the rules that matter. We rewrite the logic buried in old custom code on purpose, with the staff who depend on it, and retire what nobody uses.
- Keep the connections working. We test the membership system, the CRM, payments, and sign-on against the new site before launch.
How it runs
Your editors agree to a short freeze, and someone on your side answers "is this page still true?" for each group of pages. You choose the launch week, away from your busy season. Rewriting every PDF from 2009 is a different project, and we will say so when the file list makes that obvious. The order we use for membership sites is in planning a membership site migration.
Leonardo has done this work on the sites on the experience page. BOMA San Francisco went through several rebuilds between 2004 and 2026 while its membership systems changed, and it runs on Drupal 11 today. The M3AAWG site has been upgraded across major Drupal versions since 2009 and also runs on Drupal 11. OLLI at UC Berkeley was rebuilt from the workflows its staff already knew.
Who this fits: Associations, Educational institutions, Foundations, Nonprofits, Small businesses. Prices are on the pricing page.