# inbuxa-migrate
> [!NOTE] > Development happens on [git.coffeylabs.org/inbuxa/inbuxa-migrate](https://git.coffeylabs.org/inbuxa/inbuxa-migrate); the copy on GitHub is a read-only mirror. > Report issues at **[git.coffeylabs.org/inbuxa/inbuxa-migrate/issues](https://git.coffeylabs.org/inbuxa/inbuxa-migrate/issues)**, join discussions at **[community.coffeylabs.org](https://community.coffeylabs.org)**, or chat on **[Discord](https://discord.gg/nqcY4TKfAn)**. One program that moves an account into **inbuxa**: its mail, calendars, contacts, identities, Sieve scripts and files. inbuxa-migrate import imap … alice.sqlite an account into an archive inbuxa-migrate inspect alice.sqlite what landed inbuxa-migrate export … alice.sqlite the archive into inbuxa inbuxa-migrate export-files alice.sqlite out the archive as plain files inbuxa-migrate import files out alice.sqlite those files read back, manifest and all inbuxa-migrate export-imap … alice.sqlite its mail into any IMAP server inbuxa-migrate export-managesieve … alice.sqlite its filters, likewise inbuxa-migrate export-caldav … alice.sqlite its calendars into any CalDAV server inbuxa-migrate export-carddav … alice.sqlite its contacts into any CardDAV server inbuxa-migrate export-directory … out a server's accounts, no secrets inbuxa-migrate import-directory … out those accounts, set up on inbuxa inbuxa-migrate migrate --plan plan.json work many accounts, by a plan inbuxa-migrate guide work the same, walked through in the browser Between the two sides sits an archive: one SQLite file holding one account. `import` fills it from the old server; `export` writes it into the new one. Import and export never talk to each other, only to the archive, so the old server can be gone before the new one exists. Both commands converge. An interrupted run picks up where it stopped, and a later `import` into the same archive adds what arrived since. Every command takes `--dry-run` and then only reports the plan. An `import` also takes `--estimate`, which connects to the source and reports how much is new to fetch — counts, bytes and a rough time — before committing, and writes nothing. It reports sizes for `imap`, `maildir`, `caldav`, `carddav`, Exchange (`ews`) and a `takeout` (whose files it reads to count the mail, events and contacts that are new). For `jmap` and Microsoft Graph it reports counts only: the enumeration gives the new-object count for free, but a size there would cost a body fetch per object. The remaining sources fall back to a plain dry-run. `inspect` reads an archive and changes nothing. The archive is also a backup. Import on a schedule, keep the file, and restore it later with `export`. An archive remembers which account filled it and refuses a different one unless told otherwise. Export speaks JMAP only. It writes into inbuxa, or into any JMAP server that advertises the types being written. `export-imap` writes the mail into any IMAP server, `export-managesieve` the Sieve filters into any ManageSieve server, `export-caldav` and `export-carddav` the calendars and contacts into any CalDAV and CardDAV server, and `export-files` is the way out to everything else: it writes the archive as a Maildir++ tree, vCard, iCalendar and Sieve files that other servers and mail, calendar and contacts apps open, with no network and no store format in the way, and `import files` reads such a tree back whole. For a whole server, `export-directory` writes the list of domains, accounts, groups, lists and aliases to set up again elsewhere, without passwords, and `import-directory` sets them up on an inbuxa server, with a new password for each user. `migrate` moves many accounts with one plan file: the same steps for each account, several at once, resuming where it stopped, with one report at the end. With `--repeat` it keeps syncing, each pass moving only what arrived since, so the new server stays close behind the old one until the cutover. `guide` walks through the same move in the browser: it asks where the mail is, which accounts and which inbuxa server, previews, and runs the plan it writes. The full command reference is in [docs/usage.md](docs/usage.md). ## Sources - **JMAP** -- any JMAP account, including an inbuxa or Stalwart server. - **IMAP** -- mail only. Folders are chosen by name or by pattern. - **CalDAV, CardDAV** -- calendars and events, address books and contacts. - **WebDAV** -- a plain file collection, kept as a file tree. - **ManageSieve** -- Sieve scripts only, with the active one recorded. - **Maildir** -- a local Maildir++ tree. No network. - **Google Takeout** -- the `.mbox`, `.ics` and `.vcf` files in a Takeout export, or in any directory tree laid out that way. - **Exchange Server** -- an on-premises mailbox, through EWS. - **Exchange Online** -- through Microsoft Graph. EWS is being retired in Exchange Online: blocked from October 1, 2026 unless an administrator allows the client, and switched off on April 1, 2027. Public folders are only reachable through EWS. ## Credentials Secrets are read from the environment, or asked for at a prompt: INBUXA_MIGRATE_PASSWORD a password for --auth-basic INBUXA_MIGRATE_API_KEY an API key or bearer token for --auth-bearer (INBUXA_MIGRATE_TOKEN still works) INBUXA_MIGRATE_EWS_CLIENT_SECRET the OAuth client secret for app-only EWS INBUXA_MIGRATE_GRAPH_TOKEN a Microsoft Graph access token INBUXA_MIGRATE_GOOGLE_KEY a Google service account's JSON key, for --google-key-from-env Any of these can instead be read from a file, by setting the same name with `_FILE` appended to the file's path -- the Docker, Compose and systemd secrets convention: INBUXA_MIGRATE_PASSWORD_FILE=/run/secrets/imap-password INBUXA_MIGRATE_API_KEY_FILE=/run/secrets/token The file holds the secret and nothing else; one trailing newline is ignored. Setting both a variable and its `_FILE` form is an error. (A Google key is already a file: `--google-key