Junyr Migration Wizard: Import Gmail, Outlook & CSV into a Sovereign Inbox

A guided 6-step wizard that imports your Gmail, Outlook, or CSV/MBOX/EML history into your own European-hosted Junyr mailbox — streaming, deduplicated, resumable, and a one-time import rather than a permanent sync.

Junyr Migration Wizard: Import Gmail, Outlook & CSV into a Sovereign Inbox

In short — The Junyr Migration Wizard is a 6-step flow that imports your existing email from Gmail, Outlook, or a CSV/MBOX/EML export into your own sovereign Junyr (Stalwart) mailbox — over OAuth IMAP for Gmail and Outlook, with streaming import, Message-ID deduplication, folder mapping, and resume-on-interruption. It's a one-time import, not a permanent sync, and your history lands on European, sovereign infrastructure.

Switching email platforms usually means leaving years of history behind — or paying someone to wrestle with IMAP exports. The Junyr Suite, the sovereign AI operating system for your business, ships a built-in Migration Wizard so you can bring your inbox with you in a few clicks. This article walks through how it works, what it imports, and why "your data, your mailbox" matters.

---

TL;DR: What the Migration Wizard does

---

Why migration is the hard part of switching email

For most small businesses, the inbox is the archive. Quotes, contracts, supplier threads, customer history — it all lives in Gmail or Outlook. The fear of losing that history is the single biggest reason people stay on a platform they've outgrown.

The Junyr Migration Wizard removes that friction. Instead of exporting .mbox files by hand, fighting IMAP credentials, and hoping nothing duplicates, you run a guided 6-step wizard. Your messages stream into a mailbox you actually own — hosted in Europe, on the same sovereign infrastructure that powers the rest of the Junyr Suite.

This is the front door to everything else: once your mail is in Junyr, the inbox-first ERP, the Morning Briefing, the entity-graph CRM, and Ask Junyr all start working on your real correspondence.

---

How it works: the 6 steps

The wizard is a single, linear flow. You can leave and come back — an import that's already running shows up as a dashboard-wide banner so you're never wondering whether it finished.

1. Pick your source. Gmail, Outlook, or upload a file (CSV, MBOX, or EML).
2. Connect (Gmail / Outlook only). You authorize Junyr to read your mailbox over OAuth IMAP. This is the only place Google or Microsoft sign-in is used in Junyr — purely to fetch your existing mail. There is no Google login for the app itself.
3. Choose the destination mailbox. Import into an existing Junyr inbox, or create a fresh one on the spot.
4. Map your folders. The wizard knows each provider's layout and lines up Inbox → Inbox, Sent → Sent, Archive → Archive, and so on.
5. Run the import. Messages stream in one at a time. Duplicates are skipped by Message-ID, so re-running a partial import never doubles your inbox.
6. Review the result. A summary shows what came across — including any messages skipped or with parse errors flagged for transparency.

Gmail / Outlook (OAuth IMAP)  ─┐
CSV / MBOX / EML (upload)      ─┼──▶  Streaming import
                                │      • Message-ID dedup
                                │      • per-provider folder map
                                │      • resumable
                                ▼
              Your sovereign Junyr (Stalwart) mailbox — European-hosted

---

A one-time import — not a permanent sync

This is the part worth being precise about: the Migration Wizard performs a one-time import. It is not a continuous Gmail or Outlook sync.

That's a deliberate sovereignty choice. The point of migrating is to move your correspondence onto infrastructure you control, then keep working there. After the import completes, the OAuth tokens used to read Gmail or Outlook are erased — Junyr doesn't keep a standing connection to your old provider, and there's nothing left phoning home to Google or Microsoft.

If you keep receiving new mail at your old address during the transition, you re-run the wizard (Message-ID dedup means only the new messages come across), or you set up forwarding from the old provider into your new Junyr inbox.

---

Where your data lands: a sovereign mailbox

The destination is the whole point. Your imported mail goes into a Junyr (Stalwart) mailbox — a professional inbox on European-hosted, sovereign infrastructure, the same one every human and Junyr Agent on your team can have.

If you point the import at an inbox running one of Junyr's stricter confidentiality tiers, your sovereignty posture comes along for the ride. The Junyr Suite offers three per-inbox AI processing modes — Simple, Sécurisée, and Totale — so you decide, mailbox by mailbox, how much the AI ever touches. For the full breakdown, read the 3 confidentiality levels per inbox.

For teams that want to go further, the Junyr Suite also supports bringing your own local LLM (so eligible AI runs on your own hardware) and an On-Prem self-hosting option — the sovereignty pillars that sit alongside European hosting.

---

A concrete example

Say you're a 4-person agency on Gmail with eight years of project history:

• You open the Migration Wizard and pick Gmail.
• You authorize read access over OAuth IMAP (the tokens will be erased afterward).
• You create a new studio@yourcompany.com Junyr inbox as the destination.
• The wizard maps your Gmail labels to folders and starts streaming.
• Mid-import your laptop sleeps — no problem. When you return, the dashboard banner shows the job, and the import resumes rather than restarting.
• The summary screen confirms the import, listing the handful of malformed legacy messages it flagged.

From that moment, your eight years of threads are in a mailbox you own — and the inbox-first cockpit (Briefing, CRM, Ask Junyr) is working on your real data.

---

Going further

• Files, not just providers. No Gmail or Outlook account in the loop? Export your old mail as MBOX or EML, or bring contacts/records as CSV, and upload directly.
• Create the inbox during migration. You don't need to provision the destination first — the wizard can create a fresh Junyr mailbox as part of the flow.
• One import at a time. The wizard runs a single import per user at a time, which keeps the streaming pipeline stable and the dedup deterministic.

See what's included on the pricing page — note that guided migration is a flat €1,490 excl. VAT (revenue < €5M; on quote above) — or explore the Junyr Suite.

---

FAQ

Can I import my Gmail and Outlook emails into Junyr?

Yes. The Junyr Migration Wizard imports Gmail and Outlook mailboxes over OAuth IMAP — a guided 6-step flow that streams your messages into your own sovereign Junyr mailbox, deduplicating by Message-ID and mapping your folders automatically. You can also upload CSV, MBOX, or EML files instead.

Is this a permanent sync with Gmail or Outlook?

No — it's a one-time import, not a continuous sync. After the import completes, the OAuth tokens used to read your old mailbox are erased, so Junyr keeps no standing connection to Google or Microsoft. To bring across mail that arrives later, you re-run the wizard or forward from your old provider.

Does Junyr use Google or Microsoft login?

No. The only place Gmail or Outlook OAuth is used is the Migration Wizard, purely to read your existing mail for the import. There is no Google or Microsoft sign-in for the app itself — you log into Junyr with your own credentials and optional WebAuthn passkey 2FA.

What happens if the import is interrupted?

The import resumes. The Migration Wizard streams messages one at a time and tracks progress, so an interrupted job picks up where it left off — and a dashboard banner shows any import that's still running. Message-ID deduplication means re-running never duplicates messages already brought across.

---

Bring your inbox with you, onto infrastructure you own. Updated 2026-06-14.