Zenbe Is Gone: 6 GTD Email and List Swaps

Zenbe is gone, and so is the app its list users were told to move to. That double shutdown is the whole story, and it is the part the old blog posts still floating around Google will not tell you: Zenbe Mail and Zenbe Lists were closed down in the early 2010s, there is no login screen, no archive and no successor from the original team. Zenbe Lists refugees were widely pointed at Wunderlist, which Microsoft then retired on 6 May 2020, pushing everyone to Microsoft To Do. Two forced rebuilds in under a decade.
This piece does two things. It gives you the honest status of Zenbe, then names six live replacements, split between the two very different jobs Zenbe was trying to do at once: a shared, commentable inbox and a stripped-back list app. The conclusion up front, so you can stop reading if you already agree: if you are the only person in your system, buy a plain standards-based mailbox and a separate list app. Do not buy a team inbox.
What happened to Zenbe (and which Zenbe you probably mean)
Zenbe launched around 2007 as a web mail client with a genuinely novel idea: one inbox that several people could work in, with comments attached to individual messages rather than buried in a reply-all chain. Zenbe Lists came later as a companion app, a simple shared to-do list that synced between browser and phone. Both were retired in the early 2010s. Accounts were closed, data was not migrated anywhere, and the company did not hand the product to a new owner.
The name collisions you will hit in search
Search “zenbe”today and the results are a mess. A Steam survival game, a Japanese ryokan, an anime character and an unrelated social media scheduling tool all share some form of the name. None of them is the email app. If you arrived here from an old bookmark, a 2010 forum thread or a link in a GTD blog archive, the product you remember is the one that no longer exists.
Why the old reviews still rank
Zenbe got real tech-press coverage at the time, and those pages still carry authority. They describe an interface, a pricing model and a sync behaviour that exist nowhere now. Age is not the only problem. Nothing has replaced those pages with a clear “this is dead”statement, so the reviews keep ranking and keep sending people to a landing page that no longer resolves to a product.
What Zenbe actually got right
Worth naming precisely, because it tells you what to shop for. One: a shared inbox where a message could be discussed inline by the two or three people who handled it. Two: a list app light enough that adding an item took a couple of seconds on a phone in 2010, on 3G, which was harder than it sounds. Most modern task apps are heavier than Zenbe Lists was.
And here is the design flaw that made the shutdown hurt twice. Zenbe merged two jobs into one vendor. In a working GTD system your email is a capture channel and your list manager is a separate thing entirely. Keep them apart and no single company’s closure can take out your action lists.
The five jobs a Zenbe replacement has to do
Feature tables are useless here. Score candidates on jobs instead.
- Time-to-captured. Seconds from thought to stored item, on a locked phone, without opening a project view first. If it takes more than about five seconds you will stop doing it under pressure. That is a practical working benchmark rather than an official rule, and it is the same test used in our guide to capturing ideas in under five seconds.
- One trusted inbox. A single place things land. Two inboxes means things hide in the one you are not looking at.
- Retrieval from half a memory. You remember two words and roughly when. Can you find it?
- Exit cost. How much of your data leaves in a format another app can read.
- Daily admin tax. How much tagging, status-setting and tidying the tool demands before it earns its keep.
Zenbe scored well on the first two and catastrophically on exit cost. Weigh exit cost first from now on.
Three swaps for Zenbe Mail: the collaborative inbox
1. Spark Mail
Spark is the middle option: a polished mail client with team features bolted on, rather than a support desk pretending to be a mailbox. Comments on threads, shared drafts, send later and a snooze model that pairs neatly with a weekly review, because a snoozed message returns to the inbox instead of rotting in a “starred”pile.
Best for
- Two to four people sharing a mailbox occasionally, not all day
- Readers who liked Zenbe’s inline comments but do not want per-seat pricing
- Anyone who wants snooze plus scheduled send in one client
Pros
- Free tier covers solo use; paid team plans are modest
- Connects to your existing IMAP or Gmail account, so switching clients later is cheap
- Fast capture of a message into a task via other apps’ share sheets
Cons
- Comments and shared drafts live in Spark’s own layer, not in the mailbox, so they do not survive a move
- Its built-in tasks are not a list manager; treat them as temporary
- Feature set has shifted several times across versions, so check what is current before committing
2. Missive
Missive is the closest surviving relative to what Zenbe Mail was doing: a shared inbox with real conversation threads attached to messages, assignment, and rules for who handles what. Priced per user per month, so the bill scales with the size of your team. Check the current pricing page.
Best for
- A small team processing one address together every day, such as hello@ or bookings@
- Replacing internal forwarding and “did you reply to this?”messages
Pros
- Genuine inline discussion, the Zenbe behaviour people actually miss
- Clear assignment so a message has one owner
- Works over your existing mail provider
Cons
- Overkill for a one-person system, and you pay monthly for the privilege
- Adds a daily admin tax: assigning, closing and commenting only pays off with two or more people in the same mailbox
- The collaboration data is proprietary, even though the mail itself is not
3. Fastmail
The boring, durable choice, and the one most solo readers should take. A paid individual plan, full IMAP access, standards-based calendars and contacts, and no attempt to be your task manager. Your exit cost stays close to zero because any client can read it.
Best for
- Solo practitioners who want a mailbox, not a workflow product
- Anyone burned by a shutdown who wants their mail portable by default
Pros
- IMAP means you pick the client: Apple Mail, Thunderbird, Spark, whatever you like next year
- Thunderbird can pull the whole account down to mbox files for a local archive
- Search is quick and handles the “two words and roughly when”test well
Cons
- No shared inbox comments at all
- Paid only, with no free tier
- You supply the discipline; the app will not nag you into processing
Deciding between the three takes one question. Is anyone else reading this mailbox? If no, buy a mailbox and pair it with a client you like. If you want to compare clients properly, our comparison of Mac email apps for getting things done scores them on processing speed rather than feature count. And if you remember Sparrow, our Sparrow write-up is a second case study in the same lesson.
Three swaps for Zenbe Lists: simple shared task lists
4. Microsoft To Do
The direct heir to Wunderlist, built by the team Microsoft acquired, and free with a Microsoft account. If you followed the Zenbe Lists to Wunderlist path and then stalled in 2020, this is where that road ends.
Best for
- Shared household or small-team lists (shopping, packing, handover)
- Anyone who wants Wunderlist behaviour back at no cost
Pros
- Free, cross-platform, and shared lists work the way Zenbe Lists users wanted
- My Day view gives a daily short list without building a filter system
- Steps (subtasks) and file attachments included
Cons
- Weak review views; no proper contexts, so you improvise with lists
- Export is awkward compared with CSV-per-project tools
- Its history is literally a shutdown chain, so keep a plain-text backup of your next actions
5. Todoist
The fastest capture of the three. Type “call Dave friday 9am @calls”and quick-add parses it into a dated task with a label. Contexts live as labels, and filters rebuild GTD views. The useful version is a subscription, cheaper when billed annually; check the current pricing page.
Best for
- Practitioners running proper contexts and a weekly review
- Heavy keyboard users who capture by typing, not tapping
Pros
- Natural-language dates cut time-to-captured to a couple of seconds
- CSV export per project, which makes a future migration an evening’s work
- Filters give you context lists without a plugin ecosystem
Cons
- Free tier limits reminders and project count; the useful version is paid
- Labels and filters invite fiddling, which is a daily admin tax if you let it grow
- Attachments and comments sit behind the paid plan
6. Apple Reminders
Free on Mac and iPhone, and quietly the most standards-friendly list app on this page: it syncs over CalDAV, and dates follow the iCalendar conventions. Sensible if you already live in Apple Mail and Calendar.
Best for
- Apple-only households who want zero subscriptions
- Location and time reminders (“when I get to the office”)
Pros
- Capture via Siri with the phone locked, which is the real test condition
- Shared lists, subtasks, tags and smart lists included at no cost
- CalDAV underneath, so a third-party client can read your data
Cons
- No tidy CSV export; you script it or copy it out
- Windows and Android access is poor to non-existent
- Review views are basic next to a filter-driven app
Losses, plainly: Microsoft To Do gives up contexts and review views, Todoist gives up being free, Reminders gives up cross-platform and clean export. Pick the loss you can live with. If your lists are entangled with notes, the note taking apps scored for a GTD workflow piece covers where the boundary should sit.
Rebuilding your GTD setup after a shutdown
Start by separating the two jobs Zenbe merged. Email is an in-tray. It is not an action list. Processing a message means deciding the next action and writing that action in your list app, then filing or deleting the message. Starring is not processing; it is postponement with a badge.
A realistic one-evening rebuild looks like this: about 30 minutes choosing your mailbox and list app, 30 minutes creating a small set of contexts (@calls, @errands, @mac, @waiting), then 60 to 90 minutes taking the inbox to zero with the two-minute rule (do it now if it takes under two minutes, otherwise capture the action and file the mail). Finish by putting a recurring 45-minute weekly review in your calendar. Not a reminder. A calendar block.
Resist the elaborate label tree. Four or five folders plus search beats forty nested labels, because search handles retrieval and folders only need to handle the handful of things you genuinely revisit. Reference material should leave email entirely and live in your notes app.
As for your old Zenbe data: it is unrecoverable. No archive, no export request, no support address. Rebuild from what you have now, which is your current inbox, your calendar and your head.
How to avoid the next migration chain
The Zenbe Lists to Wunderlist to Microsoft To Do chain shows where the cost really sits. Not the monthly fee. The repeated rebuilds, each one eating an evening and quietly losing the habits you had attached to the old tool.
So run the export before you commit, not after. Create three test items, export them, and open the file in Numbers, Excel or a text editor. Todoist hands you CSV per project. Apple Reminders syncs over CalDAV. Thunderbird will pull an IMAP mailbox down to mbox for archiving. If the export cannot be read outside the app, treat that tool as temporary however good the capture feels. Our write-up on what a Notion export actually loses shows how far a technically real export can still fall short.
Warning signs worth taking seriously: no paid tier at all (someone has to fund the servers), sync that only works between the vendor’s own apps, and a single funding round with no revenue story. None of those is proof of doom. All of them raise the odds.
Keep a fallback that no company can switch off. A text file of next actions in a synced folder costs nothing and opens in 2045. So does paper: an hPDA card in your back pocket has never once shown a retirement notice. The durable layer is the standards layer, and the standards layer is why a rebuild takes an evening rather than a fortnight.
Frequently Asked Questions
Is Zenbe still available, and can I log in to my old account?
No. Zenbe Mail and Zenbe Lists were shut down in the early 2010s and there is no working login, support channel or successor product from the original team. Any page promising a Zenbe sign-in today is either an old cached result or a different company that happens to share the name.
What happened to Zenbe Lists after it shut down?
Users were widely advised to move to Wunderlist, which was the obvious like-for-like at the time. Microsoft later acquired Wunderlist and retired it on 6 May 2020, directing people to Microsoft To Do. That is two forced migrations for anyone who started on Zenbe Lists.
Can I recover my Zenbe email or list data?
Realistically, no. The service closed without a migration path and there is no archive to request data from. If any Zenbe mail was collected over POP or IMAP into a desktop client years ago, check that client’s local folders, because that is the only place a copy could plausibly survive.
Which Zenbe alternative works best for a GTD system?
For most solo practitioners: a standards-based mailbox such as Fastmail paired with Todoist or Apple Reminders for lists. The mailbox handles capture, the list app handles next actions, and neither vendor’s closure takes out the other half of your system.
Do I need a shared inbox tool, or just a better email client?
If you are the only person reading the mailbox, a better client. Comments, assignments and internal threads are a daily admin tax that only pays off when two or more people process the same address. Add a shared inbox tool the day a second person starts replying, not before.
