Creating a customer over the API always notifies them, and omitting the password does not silence it — it selects a "set your password" template instead of the welcome one. There is no quiet-create route. The obvious workaround fails too: the global mail switch is implemented as a plugin that does not proceed, so the message is discarded, not queued. There is no spool to flush afterwards, and the same switch silences order confirmations, which matters when customers are loaded into a shop that is already trading.
Typical impact: a migration of 40,000 customers stops being a choice between mailing everyone from a domain with no sending reputation on import day, and silencing mail globally and losing it. Account mail is held during the load and released deliberately, per website or per creation date, when the shop is ready.
Who it is for
- Migrations from another platform, where password hashes cannot come across — the only create route takes plaintext or nothing, and plaintext crosses the integration boundary, sits in the export and lands in request logging.
- Any ERP feed that creates customers in a shop that is not live yet, or is live and must keep sending order confirmations while account mail waits.
- Anyone who needs the mail to arrive in the right language: the account email resolves from the customer’s own store, so an import that omits the store mails everyone in the default store view’s language.
Who should skip it
- Small imports where mailing everyone at once is acceptable. Accepting the send is a legitimate choice and needs no module.
- Shops that create customers only through the storefront, where the notification is exactly what should happen.
What it does
Two halves. During the load it suppresses account mail only, leaving every other transactional message alone. Afterwards a CLI command releases what was held, filtered the way a migration actually needs:
bin/magento brocode:customer-mail:release --dry-run
bin/magento brocode:customer-mail:release --customer=1234
bin/magento brocode:customer-mail:release --website=1 --created-after=2026-08-01 --sleep=200
It also supports a migration-specific template, so a moved customer reads "your account came with us" rather than a welcome message for an account they have had for years.
The throttle that eats a batch
This is the part that leads most people to discover the problem the hard way. Core throttles password resets, and a bulk release runs straight into it: a CLI process has no remote address, so every send is recorded with an empty one and the quantity cap applies to the whole batch rather than per customer. Measured on 2.4.8-p5, a batch of six sent one and failed five.
Sleeping between sends does not help, because the limit is a count inside a window rather than a rate. Switching the reset protection to By Email for the duration does:
bin/magento config:set customer/password/password_reset_protection_type 3
bin/magento cache:flush
bin/magento brocode:customer-mail:release --website=1 --created-after=2026-08-01
bin/magento config:set customer/password/password_reset_protection_type 1
Installation
composer require brocode/module-customer-migration-mail
bin/magento module:enable BroCode_CustomerMigrationMail
bin/magento setup:upgrade
bin/magento setup:di:compile
Compatibility
Magento 2 Open Source, verified on 2.4.8-p5. Password policy and mail policy are one decision, not two — the module assumes the shape where customers are created without a password and each sets their own.
FAQ
Can I import the old password hashes instead and skip all this?
No. The method that accepts a pre-hashed password exists but has no route; the only create route takes plaintext or nothing.
Why not just disable mail globally during the import?
Because that discards rather than defers, and it silences order confirmations too. There is nothing to flush afterwards.
Does it help with newsletter consent?
No, and mind that separately: the newsletter module ships no web API at all, so consent travels only as an extension attribute on the customer. Getting it wrong either drops an opted-in base or subscribes people who never agreed.
Related reading
- Magento Integration Skills — the customer skill covering scope, groups, addresses and this mail decision.
- Generating a Magento Agent Skill From the API Definitions — why none of this appears in the API’s own description of itself.