Userlist: company relationships, imports and billing

Count stored users over the billing window

Forecast the stored audience, including inactive users, before comparing prices. The billing window matters when the population falls.

Userlist pricing counts all stored users, even without recent activity, and uses the prior 30-day high-water mark for the monthly fee. Userlist Basic includes company accounts.

Removing inactive users may not lower the current bill while the higher count remains in that window. Preserve records needed for reconciliation before deleting anything, and model the billing window against your expected audience changes.

Map users to the companies they belong to

Choose a data model that reflects how people participate in accounts. A person’s role can differ across companies, changing which message should reach them.

Userlist’s company guide supports one-to-many and many-to-many user and company relationships. Userlist can attach properties and events to a user, a company or their relationship.

For example, a person can hold different roles at two companies. Map each relationship separately, then inspect both roles after import rather than checking only that the person exists.

For complex relationships, Userlist’s import guide recommends the API or Segment integration. Assign an owner to the mapping and test the relationship data with synthetic records before activating messages.

Reconcile identity and permission

Keep the original permission record separate from identity matching. A successful match does not tell you whether the imported subscription preference reflects the source.

Userlist’s import guide matches an imported user by identifier before email and creates a record only if neither matches. Include a duplicate email and identifier pair in the trial and inspect the resulting record.

Userlist treats imported users as opted in even when double opt-in is enabled. Preserve the original permission records and reconcile preferences before sending. Test an unsubscribed fixture with sending paused and record any difference that needs correction.

Review segments before adding leads

Review entry rules when a marketing list joins existing product users. A segment built around customers can include a different audience after the import.

Userlist’s migration guide recommends auditing forms, segments and campaigns before recreating the required setup. Userlist also warns that customer-only assumptions and first-seen onboarding triggers need review when leads are added.

Compare a dormant customer with a new lead using your intended eligibility rules. Inspect their campaign entries before enabling sends, and record who will resolve any unexpected entry. Keep the original export until the team has reconciled the migration.

How to compare the alternatives

Consider Customer.io if its profile model and mapped CSV preview fit your workload. Consider Loops if published transactional templates and its subscription model fit your application.

The Customer.io alternatives comparison compares the choices for a team considering a move. The lifecycle email buying guide offers a shared migration worksheet.

Common questions

Does Userlist count inactive users?

Userlist pricing counts all stored users, including those without recent activity.

Will deleting users immediately lower my Userlist bill?

Userlist pricing uses the prior 30-day high-water mark, so removing users may not reduce the current bill.

Are imported Userlist users opted in?

Userlist’s import guide says imported users are treated as opted in even when double opt-in is enabled.

Is Userlist the best lifecycle email tool for B2B?

Consider Userlist if relationship-level roles drive targeting across company accounts, and test your own mapping before deciding.

Sources and scope

We read the linked vendor documentation on October 29, 2026.

We have not run the product or tested migration, delivery or support.