Notes from building the migration engine
Engineering write-ups from real work on this product — specific bugs, real numbers, and what we changed. Not generic content marketing.
Why large PST migrations need a disk-space budget, not just a file copy
A mailbox migration tool that copies a PST twice before touching it can quietly need 3x the mailbox's size in free disk space — and nobody notices until it's a 100 GB mailbox on a laptop with 40 GB free.
Read post →The shared-PC problem: migrating multiple Outlook accounts off one machine
Factory and warehouse PCs are often shared across shifts, each person with their own POP3 account in the same Outlook profile. Most migration tooling assumes one PC, one mailbox — and gets quietly wrong results when that's not true.
Read post →An old registry trick that silently breaks Outlook 2010 migrations
Outlook stores account details in the registry, and most tooling reads them expecting plain text. Older Outlook installs sometimes store the same fields as raw binary instead — and a naive read doesn't error, it just quietly returns nothing.
Read post →