IMAP, POP, and hosted mail: email protocols explained for business owners

The three mail protocols differ in one decisive way: where the mail lives, and that answer decides what migration, backup, and a drowned phone actually mean.

The migration conversation starts with a question most owners have never been asked: is your mail on IMAP, POP, or a hosted account on a company server? The question sounds like plumbing, and it decides nearly everything about the move: how long it takes, what can be lost inside it, and what the quote should have said in the first place. So it is worth explaining in plain words what the protocol actually is.

The protocol is the agreement about how your device and the mail server talk, and the three models differ in one decisive way: where the mail lives. IMAP keeps mail on the server and syncs every device to it, so a message read on the phone reads as opened on the laptop, and deleting it once deletes it everywhere. POP pulls mail down to one device and usually deletes it from the server, which means mail becomes trapped on whatever machine downloaded it. Hosted business accounts, the server based model, keep mail, calendar, and contacts together on the server with the company in control.

Why should an owner care? Because the protocol decides what migration means. Moving an IMAP account is copying a library: the shelves stay intact, the copy is checked against the original, and nothing is lost if the move is done patiently. Moving a POP account is rescuing whatever survived on one device: years of correspondence that exists only because one laptop never crashed. The two jobs share almost nothing, including cost, time, and risk.

The protocol also decides what backup means, and what happens when a phone falls in the sea. Server mail backs up once, centrally, and restoring it restores it for everyone. POP mail backs up per device, per person, which in practice means per however diligent each person happens to be. The assistant whose mailbox lived on her desktop and whose calendar lived nowhere at all is not a rare story; it is the default story wherever POP lingered.

The failure versions arrive on a schedule of their own. The company that ran on POP for years and lost the only copy of its correspondence with the one laptop, along with the context of a decade of deals. The migration quoted for IMAP that doubled in time and effort when the first mailbox turned out to be POP, with folders stored in places the estimate never imagined. The team that shared a single POP account by taking turns, and nobody can say who deleted what.

The practice is short. Find out what you are on: any provider can tell you from the account settings, and it takes minutes. Prefer server side mail for company accounts, because the company, not a device, should hold the correspondence. And let the answer shape the migration and backup plan before the move starts, rather than discovering it halfway through, when folders are already scattered and the old server is already scheduled to close.

Where Bloom sits is the migration done in that order: we ask about the protocol first, size the move honestly, and put the plan in writing before anything is transferred, because discovering a POP mailbox mid migration is a planning failure, not a surprise act of nature. Specifics of any provider belong to its documentation, and unusual setups belong with a specialist before the move, not after. Guidance, not guarantees: mail can be moved carefully, and the time to know where it lives is before the boat leaves.