# Migrate from Mailtrap

> Why teams move from Mailtrap to Facteur, what switching changes in your tests, the steps to do it, and prices read at their source.
> https://facteur.eu/en/alternatives/mailtrap

Migrate from Mailtrap

## Migrate from Mailtrap

Email and SMS testing hosted in France, where the number of inboxes does not depend on the subscription tier and SSO is not reserved for the top of the range. Here is what switching changes in your tests, line by line.

- Unlimited inboxes from the Team plan
- Volume bought separately, in packs valid for a year
- Data in France, billed in euros, DPA online

## What makes a team move

- **The inbox count stops being a tier** : With them, the plan decides how many sandboxes you open. A team that wants one inbox per branch finds out quickly: the volume holds, and it is the inbox counter that triggers the upgrade.
- **SSO does not cost a change of range** : SAML is included from our Team plan. It is often IT’s only line item, and it should not decide the rest of the bill.
- **No more artificial waiting in tests** : One call blocks until the message lands, then hands back the body, the links and the code already extracted. The polling loops and the sleeps leave your suites.
- **A quota per inbox, with its alert** : A runaway test eats the whole organisation’s capacity with nobody seeing it before the invoice. A per-inbox ceiling and an alert threshold settle it at the source.

## Translating your tests

The Mailtrap client lists an inbox’s messages, then asks for the body; waiting for the right one to have arrived, and finding the code in it, is left to you. Here it is one call that waits and hands the message back in pieces.

## The migration, step by step

Nothing is transferred: test messages regenerate on your suite’s next run. Both services can run side by side until everything is green.

- **Create an account and an inbox** : Every inbox gets its own subdomain, and any address ending in it is accepted from the first message. There is nothing else to provision.
- **Point your sends at the inbox** : Where Mailtrap captures your application’s SMTP traffic, your scenarios now write to a public address of the inbox: the message travels the real sending path, the one a user would see.
- **Replace the calls in the tests** : Listing the messages, and the sleep before it, become a single messages.waitFor() that blocks until arrival and hands back the body, the links and the code already extracted.
- **Run the suite, then cancel** : Keep both accounts until the suite is green: there is no data to export and no DNS to switch, so nothing forces the pace.

The switch, at a glance

- Inboxes
- Unlimited from the Team plan
- Sandbox count set by the plan

- SAML SSO
- Included from the Team plan
- Reserved for higher plans

- Message volume
- Bought separately, in stacking packs
- Set by the subscription tier

- Per-inbox quotas
- Yes, with overage alerts
- Not documented

- Transactional sending
- No, we only receive
- Yes, a dedicated product

- Hosting
- France, billed in euros
- Outside France, billed in dollars

- DPA
- Downloadable online
- On request

Where this page’s claims come from

Frequently asked