The migration for a cultural institution covered three websites and its email history. The services included a booking website, so the cutover had to account for both historical data and new records created during the transition.

More than copying files

We began by inventorying the websites, databases, mailboxes and configuration. Our scope covered the files for three websites, three MySQL databases, scheduled tasks, application email and user mailboxes. We prepared copies outside the source environment, then moved the websites and their configuration to new hosting.

For the websites, we configured HTTPS and CRON jobs. We transferred the applications’ SMTP settings and configured mail records, including SPF and DKIM.

One destination for new records during cutover

Running two independent copies of a booking website could split new records between two databases. During the transition, the old server forwarded web requests to the new environment. This kept new writes in one place, even while some visitors could still reach the previous server address.

Copies checked through a restore test

We compared the copied files and configuration with the source within the agreed scope. Restore tests for the three websites and their databases passed. They covered importing 236 tables, HTTP 200 responses and checks of selected media files. Email and configuration archives were also read back and verified using checksums.

Website restore tests and archive verification are separate checks. We do not present them as a full functional restore test of every email mailbox.

Email history without duplicating collections

We migrated the history of 21 mailboxes and the unique portion of a catch-all account. Its structure included references to other mailboxes, which had to be separated from the account’s own history to avoid copying the same collections again.

The synchronisation accounted for folder mapping and differences in letter case in folder names. Subsequent runs used the same mapping and UID cache. We retained internal message dates and existing destination flags without deleting messages from either side.

The verified synchronisation result

The final IMAP check on 19 October 2026 completed successfully for all 22 entries: 21 mailboxes and the system account holding catch-all history. The imapsync report recorded more than 35,000 messages already present at the destination, with no source messages missing and no errors. That run required no additional messages to be transferred.

We treated IMAP-history verification separately from functional acceptance of email delivery, bookings and payments. Domain transfer and DNSSEC remained separate project stages. Each reported check therefore described the scope that had actually been verified.

Planning to move websites or email?

We help inventory environments, prepare independent copies and plan migrations around data that continues to change during normal operation. Explore our Linux server administration or tell us which services you need to move.

Hosting, MySQL, Poczta E-mail
Back