A plan for one risky change

Moving the team wiki to a new host

Reading time about 7 minutesWritten 2026-10-13For: the wiki owner
The wiki is copied from the old host to the new host, and a dashed line shows the way back for a month. Old hostthe wiki today copy first New hostthe wiki after the way back, for a month

We copy the wiki to a new host, switch on one planned evening, and keep the old host for a month, so your team notices one new address.

Keep in your head (only these)
  1. Six phases. Only two reach your team.
  2. Nothing goes live without your yes.
  3. Going back takes minutes, for a month.
  1. Phase 1Decide what moves Ya few days
  2. Phase 2Copy and rehearse Mabout a day
  3. Phase 3Announce the date Yten minutes Team notices
  4. Phase 4Switch day Y+Mone evening Team notices
  5. Phase 5Watch and fix Ma week
  6. Phase 6Retire the old host Yan hour

Chapter 1 of 8, about 1 minute

What changes, and what stays the same?

Before this: the answer says the wiki moves to a new host and your team notices one new address.

Today one host does everything. After the move the new host does, and the old one stays on for a month in case we need to go back.

Before, one address leads to the old host and its pages. After, a new address leads to the new host and a copy of the pages, and the old host stays on for a month as the way back. Before old-wiki.examplethe address today Old hostruns the wiki Pages and filesall in one place After wiki.example.comthe new address New hostruns the wiki Pages and filescopied, not moved Old host, kept for a monthforwards visitors, and is our way back
Take from this: the address and the host behind it change. Nothing is taken out of the old host, only copied.

Remember: we copy and never move, and the old host stays on for a month.

Chapter 2 of 8, about 1 minute

What does your team see?

Before this: we copy the pages and the address changes.

Three moments reach your team. Everything else happens out of their sight.

old-wiki.example/handbook
Handbook OnboardingHoliday policyExpenses
Take from this: until the date is announced, nothing looks different.
team chat
From you, FridayThe wiki moves on Saturday evening. Your pages stay as they are. You will sign in once more.
Take from this: a day before, you send one message. I can draft it.
wiki.example.com/sign-in
Sign in Sign in Then the same pages as before.
Take from this: from switch day, one new address and one extra sign-in.

Remember: your team sees a message, then a new address, then one extra sign-in.

Chapter 3 of 8, about 2 minutes

What happens in each phase?

Before this: your team sees a message, a new address and one extra sign-in.

Each phase finishes before the next starts.

  1. Decide what moves

    You decideA few days
    • Pick what comes across: pages, files and comments.
    • Answer the three questions at the end of this page.

    Team notices: nothing.

  2. Copy and rehearse

    I do the workAbout a day
    • Copy everything to the new host.
    • Rehearse the move on a spare copy, then take a fresh backup.

    Team notices: nothing. The old wiki still works.

  3. Announce the date

    You send itTen minutes
    • One message with the date and the new address.

    Team notices: a message with the date and the new address.

  4. Switch day

    Both of usOne evening
    • The wiki is read-only for about an hour.
    • The new address goes live, and the old one forwards to it.

    Team notices: the new address, and one extra sign-in.

  5. Watch and fix

    I do the workA week
    • Watch for errors and broken links.
    • Fix what turns up the same day.

    Team notices: nothing new.

  6. Retire the old host

    You decideAfter a month
    • Check that nobody still uses the old address.
    • Say yes, and I switch it off.

    Team notices: nothing.

Take from this: four of the six phases happen out of your team's sight.

Remember: only phases 3 and 4 reach your team, and both are marked "Team notices".

Chapter 4 of 8, about 1 minute

What goes where?

Before this: only phases 3 and 4 reach your team, and we copy rather than move.

Where each piece of the wiki ends up
PieceOld hostNew host
Moves over
Pages and their historyKept, read-onlyCopied in full
Uploaded files and imagesKept, read-onlyCopied in full
Stays behind
Visitor statisticsKeptNot copied
Plugins nobody usesKeptLeft out
Your call
Page commentsKeptCopy them?

Take from this: two pieces stay behind on purpose, and the old host keeps all of them.

Remember: the old host keeps everything, so a piece we leave out is never lost.

Chapter 5 of 8, about 1 minute

Who does what, and what never bends?

Before this: six phases, with a part for each of us.

Y You

  • Answer the three questions below.
  • Say yes before any step that touches the live wiki.
  • Send the message to your team.
  • Decide when the old host goes.

M Me

  • Copy the wiki and rehearse the move.
  • Do each live step, after your yes.
  • Check the pages that matter, before and after.
  • Watch for errors for a week.
  • Nothing live without your yes. Every step that changes the live wiki waits for you.
  • Copy, never move. The old host keeps every page until you say it can go.
  • A backup before every switch. A fresh one, checked that it opens.
  • Rehearse first. Each live step runs on a spare copy with fake data.

Take from this: you decide and send, I copy and check.

Remember: you say yes to every live step, and the old host stays until you say it can go.

Chapter 6 of 8, about 1 minute

What happens on switch day, step by step?

Before this: I do each live step, and only after your yes.

  1. Y Send the heads-up. One message, a day before: the date and the new address.
  2. M Take a fresh backup. I check that it opens.
  3. M Make the old wiki read-only. Nobody can edit for about an hour.
  4. M Copy the last changes across. Then I check the pages that matter.
  5. Y+M Point the new address at the new host. You say yes first.
  6. M Forward the old address. Visitors to the old address land on the new one.
If something goes wrong: point the new address back at the old host and turn the forwarding off. The old host still has every page, so the wiki is back within minutes.

Take from this: one evening, six steps, and the way back is one step.

Remember: on switch day the way back is one step, because the old host still has every page.

Chapter 7 of 8, about 1 minute

What could go wrong?

Before this: the way back on switch day is one step.

The old host gets forgotten

High

It still holds every page. Left alone, it turns into the weak spot.

Kept small by: a reminder to switch it off one month after switch day.

Someone misses the message

Medium

They open the old address and wonder where the wiki went.

Kept small by: the old address forwards to the new one for a month.

Sign-in breaks on the new host

Medium

People reach the wiki but cannot log in.

Kept small by: I test sign-in on the spare copy, and again right after the switch.

A page looks different

Low

A few pages use a feature the new host handles in its own way.

Kept small by: I check the twenty most-read pages before and after.

Take from this: the one high risk is about the weeks after the move, so it has a date on the calendar.

Remember: the biggest risk is forgetting the old host, so it gets a reminder.

Chapter 8 of 8, about 2 minutes

What will it cost, and what do I need from you?

Before this: one risk is high, and it has a reminder.

$12a month for the new host
$8for the one extra month of the old host
2 hof your time, in all
$0to copy the pages and files

Take from this: running both hosts for one month is the only extra cost.

Three questions are left. Pick an answer for each. My choice is marked. The bar at the bottom copies your answers so you can paste them back to me.

Should page comments come across?

Comments are the discussion under pages. They are small, and some are useful.

Which evening should the switch happen?

The wiki is read-only for about an hour. A quiet evening costs your team the least.

How long do we keep the old host after the switch?

It is our way back, and it costs $8 a month.

Remember: three answers from you, and the copy bar at the bottom sends them back to me.

Recap

  1. We copy and never move, and the old host stays on for a month.
  2. Your team sees a message, then a new address, then one extra sign-in.
  3. Only phases 3 and 4 reach your team, and both are marked "Team notices".
  4. The old host keeps everything, so a piece we leave out is never lost.
  5. You say yes to every live step, and the old host stays until you say it can go.
  6. On switch day the way back is one step, because the old host still has every page.
  7. The biggest risk is forgetting the old host, so it gets a reminder.
  8. Three answers from you, and the copy bar at the bottom sends them back to me.