emcognito
Back to Blog

How to Switch from SimpleLogin to Emcognito Without Losing a Single Alias

October 1, 2026

Updated

simplelogin migrationemail alias service migrationemail aliasesprivacyemcognito

Keep your real inbox private.

Unlimited aliases, free. No credit card, passwordless sign-in.

Create a free alias →

The Short Answer: What Actually Moves and What Does Not

If you want to know how to switch from simplelogin to emcognito, the practical reality is straightforward: you cannot export your SimpleLogin aliases and import them directly into Emcognito. Because shared domains cannot be transferred across providers, an email alias service migration means creating new forwarding addresses on the target platform, updating your login emails on the sites that matter, and retiring dead accounts.

For inbox-safety context, FTC phishing guidance recommends treating unexpected messages and requests for personal information with caution.

Emcognito is an email alias service that creates durable, reply-capable forwarding addresses delivering to your real destination address without exposing it. It is not a disposable, temporary, or burner inbox designed to disappear after ten minutes. The underlying architectural concept carries over directly: you assign one alias per service, keep your real mailbox hidden, and shut off incoming mail the moment an address leaks.

What carries over is the organizational design. You retain isolated identities, per-site attribution, and direct inbound routing to your primary inbox. What does not carry over are the specific address strings hosted on SimpleLogin domains, any existing DNS-bound domain configurations you hold elsewhere, and platform-specific features Emcognito does not ship. Emcognito aliases use the shared emcognito.com domain. Custom subdomain support is planned, but custom domains are not available today. Furthermore, Emcognito is closed source and runs only as a hosted service; if open source or self-hosting is a requirement, addy.io is the better fit.

If you are planning a clean simplelogin migration, inspect your volume and workflow requirements on the Emcognito pricing page before updating individual site logins.

Before You Switch: Inventory the Aliases You Cannot Afford to Lose

Attempting to shift hundreds of addresses simultaneously causes verification bottlenecks and forgotten credentials. A successful migration starts with an audit. Sort your existing SimpleLogin address inventory into three distinct operational tiers:

  • Primary banking portals, utility providers, primary identity providers, and platforms accessed weekly. These require deliberate, single-site address changes with verified delivery.
  • Online retailers, software subscriptions, news feeds, and recurring services where login recovery is simple.
  • Single-purchase checkouts, closed promotional registrations, and discontinued trials. Abandon these. Recreating an address for an inactive site consumes part of your daily creation allowance without adding value.

Certain financial institutions require multi-factor phone verification or secondary identity checks before releasing an email change. Knowing which services enforce strict verification rules prevents you from being locked out halfway through a transition.

Pay close attention to whether any of your current addresses rely on sending outbound mail rather than merely receiving incoming notifications. The choice between plans rests primarily on whether you need outbound sending capabilities or pure inbound forwarding.

How to Switch from SimpleLogin to Emcognito, Step by Step

Migrating between alias platforms takes systematic execution. Follow this sequence to prevent service disruption across your services.

  1. Create your Emcognito account. Registration uses a passwordless emailed magic link. There is no password to select, no dedicated app to configure, and no complex directory structure to manage.
  2. Select your subscription tier. Choose your plan before updating addresses. If you only receive inbound messages and answer queries sent directly to you, Emcognito Free covers up to 100 forwarded messages per month alongside free replies from your delivery log. For higher forwarding volumes and outbound sending, Emcognito Plus costs $20/year ($2/month) with 2,500 forwards per month, while Emcognito Pro costs $36/year ($4/month) with 15,000 forwards per month. Pro yearly provides three months free and is the term customers actually buy.
  3. Generate the replacement alias in Emcognito. You can create aliases from the web dashboard on all plans, including Free. Mint a fresh address for your first target service and assign a clear descriptive label matching the destination platform.
  4. Update the email address on the third-party service. Log into the service, open its account settings, replace the existing SimpleLogin address with your new Emcognito address, and submit the change. Keep the site open while awaiting confirmation.
  5. Verify the routing in your real inbox. Check your primary inbox for the service's confirmation or verification link. Inspect the message envelope to confirm clean receipt through the transport pipeline as defined by standard Internet mail specifications like RFC 5321.
  6. Confirm operational receipt before touching the old alias. Leave the original SimpleLogin alias active until you have verified the change by clicking the confirmation link and receiving at least one standard operational email (such as a password update notice or login alert) through the new address.
  7. Deactivate the deprecated alias. Once delivery through Emcognito is verified, log into your SimpleLogin account and disable the old alias. If an unexpected transaction receipt arrives at SimpleLogin, you can re-enable it temporarily. Once stable, permanently delete the old record.
  8. Work in controlled batches. Update ten to fifteen sites per session. Migrating an entire digital footprint over two weeks eliminates errors and avoids exhausting daily dashboard creation allowances.

The One Capability That Decides Your Plan: Composing New Mail from an Alias

Understanding platform capabilities avoids surprises after switching. The single capability separating Emcognito Free from paid plans is composing brand-new, outbound mail initiated from an alias.

Composing brand-new mail from an alias is the only capability the Free tier cannot do at any usage level. If you only receive inbound messages and answer queries sent directly to you, Emcognito Free covers up to 100 forwarded messages per month alongside free replies from your delivery log. Starting an entirely new outbound message from an alias is reserved for paid tiers (Plus and Pro) once the initial invoice has settled.

New message composition requires a paid account whose first invoice has settled; accounts in an active trial period cannot initiate outbound messages. Outbound composition includes calibrated daily send caps: 20 sends per day on Plus and 100 sends per day on Pro, ramping up gradually across the first 7 days of an active subscription. Hitting a daily send cap does not stop inbound forwarding, but every compose send counts against the same monthly quota as forwards (2,500 messages per month on Plus and 15,000 messages per month on Pro). Composing uses up the monthly allowance that forwarding draws on.

Replying to received mail works differently. Replying to a forwarded message is included on every Emcognito plan, Free as well, and it happens in your delivery log: open the delivered message and choose Reply securely, and Emcognito sends it with the alias as the sender. Replying from your own mail app is paused for security and is refused rather than delivered. Composing a brand-new message from an alias is the Plus and Pro feature. Delivery log records from the last 7 days are accessible for replies, and each reply counts against your monthly forward quota. Source: Emcognito source.

SimpleLogin Migration: What to Check Before You Commit

Before leaving an existing setup, examine platform architectures objectively. Check SimpleLogin's public documentation and terms to ensure you do not sever integrations you actively rely on. If your current workflow depends entirely on hosting addresses under personal top-level domains, Emcognito aliases use the shared emcognito.com domain. Custom subdomain support is planned, but custom domains are not available today.

Consider the qualitative differences between the services when mapping your architecture:

Decision Criterion SimpleLogin Approach Emcognito Approach
Ecosystem Integration Integrated within a unified encrypted suite and password management ecosystem. Standalone service without bundled ecosystems, app installations, or password manager tie-ins.
Source Availability Maintains an open-source codebase supporting self-managed instances. Emcognito is closed source and runs only as a hosted service; if open source or self-hosting is a requirement, addy.io is the better fit.
Inbound Tracking Sanitation Provides configurable header handling and tracking pixel defenses. Emcognito strips tracking pixels (the tiny hidden images that report when you open a message) from forwarded mail on every plan, Free included. It does not remove scripts or rewrite links and does not scan for malware.
Outbound Reply Mechanics Reverse-alias addressing configured inside standard third-party mail clients. Delivery log secure reply initiated directly through authenticated interface.
Domain Architecture Supports bringing external domains alongside shared platform namespaces. Emcognito aliases currently use the shared emcognito.com domain. Custom subdomain support is planned, but custom domains are not available today.

For users who prefer an independent alias layer that operates outside of a browser vendor, operating system, or password vault, review the comparative breakdown on the SimpleLogin alternative overview. Reviewing monthly volume requirements remains critical: Free handles 100 forwards/month (expandable to 200 via referral credits), Plus handles 2,500, and Pro accommodates 15,000. Free accounts include a small, clearly-labelled sponsor card at the foot of incoming forwarded emails; Plus and Pro tiers strip this completely.

Organising Aliases After the Move: One Address per Site

The primary security objective of an email alias architecture is absolute sender isolation. Assigning an isolated, dedicated address to every unique web property ensures clean attribution. If an address designated exclusively for an online merchant suddenly receives unsolicited loan marketing, the leak is attributable to that specific database.

When an unauthorized sender surfaces, do not rely on standard unsubscribe links, which may validate your address to bad actors even when compliant with standards like RFC 8058. Instead, locate the alias inside your dashboard and suspend it. Suspending the alias immediately cuts off inbound delivery from all senders. The sender's mail fails to route, your inbox remains clean, and third-party databases holding that string can no longer reach you.

Any alias can be suspended with one click, and deleted after a confirmation prompt (delete is not one-click). Resuming a paused address is similarly a single dashboard click. Deleting an address permanently

Sources and further reading

Bring your aliases somewhere that lets you write back.

Replies are free on every plan. Composing a brand-new message from an alias is Plus, $20 a year.

See the plans →