Migrated customers get nudged

When you migrate subscriptions from another platform using Subi's importer, some contracts may arrive with no payment method attached — the customer's card details live in the old provider and can't be transferred directly. Those contracts are created and active in Subi, but they cannot bill until the customer adds a card.

Previously, nothing told those customers they needed to act. Their contracts would sit unbilled until they happened to log in to the customer portal, or until your team noticed and reached out manually.

Subi now handles this automatically. As soon as a migration import run finishes, Subi identifies any customers whose newly created contracts have no payment method on file and sends them a payment-method request email. Customers who already have an active card attached are skipped — they will be handled by Subi's existing card-attach flow when they next interact with the store.

A few things worth knowing about how this works:

• One email per customer, not per contract. If a single customer has multiple card-less contracts from the same import run, they receive one email, not several.
• Scoped to the current import. The email goes only to customers whose contracts were created in that run. Existing card-less contracts from other sources (such as manually created subscriptions) are not affected.
• No new configuration needed. This runs automatically as part of every migration import. There is nothing to enable or turn on.

This improvement pairs with the card-optional migration capability shipped in late July, which lets you complete an import even when customers' payment methods are not transferable upfront.