terms of use.

what these terms cover.

These terms apply to the mailexodus public website, documentation, generated migration pages, npm package, MCP server, and bundled agent skill. The open source code is provided under the repository license. Provider platforms, hosting providers, package registries, and source control platforms each have their own terms for their services.

migration responsibility.

You are responsible for the provider accounts, API keys, subscriber permissions, consent records, and destination configuration used with mailexodus. Run dry runs first, review the generated coverage report, and keep a backup of source exports before approving any write operation.

mailexodus can help map portable objects such as contacts, lists, tags, segments, custom fields, campaigns, templates, and automations. It cannot transfer sender reputation, provider trust history, live queue state, historical analytics, billing contracts, or private provider-only assets.

no production guarantee.

Migration plans and dry-run reports are provided for operational review. Provider APIs change, exports can be incomplete, and destination models may not support every source feature. Validate a sample migration before moving a full account.

The website and tools are provided as-is. To the fullest extent allowed by law, mailexodus and its maintainers are not liable for lost data, interrupted campaigns, deliverability issues, provider account actions, or business losses from using or relying on the tooling.

open source and contributions.

Code contributions, issues, and migration notes submitted to the public repository may be visible to others. Do not include API keys, subscriber data, private exports, or confidential campaign material in public contributions.

For support, open a public issue for non-sensitive questions or use the contact channel listed by the project maintainers for private operational topics.