# Imported-profile limits

Imported profiles have two holding limits under the project's current plan. The current implementation counts profiles per environment and per connection:

| Plan       | Per environment | Per connection |
| ---------- | --------------: | -------------: |
| Free       |          10,000 |          5,000 |
| Pro        |         100,000 |         20,000 |
| Business   |         250,000 |         50,000 |
| Enterprise |       1,000,000 |        200,000 |

These limits count imported profile rows, not native profiles created through ordinary sign-in. The environment count does not aggregate profiles across every environment in a project. They apply when an import adds **new** identities. The importer identifies an existing row by environment, legacy source and legacy ID. Replaying that existing identity does not consume another slot. Identical duplicates in incoming input count once; conflicting duplicates are refused.

## Create-only enforcement

The project's current plan is checked while each organization's import is committed. If positive net-new rows would exceed either limit, that organization is refused with HTTP 403 classification [`plan_limit_reached`](/errors/plan_limit_reached/). An asynchronous run records the failure in its organization state; its initial HTTP 202 response is not a quota success receipt. Other organizations can retain their completed progress. Read the import before deciding what to retry.

A downgrade does not delete existing imported profiles or prevent an existing identity from being replayed. It can prevent additional identities from being imported. Limit audit records contain counts rather than profile values. Enterprise overrides require separate configuration; a higher limit is not implied by choosing an Enterprise plan.

## Bundle limits are separate

An import bundle accepts at most 20,000 profiles per connection and 100,000 profiles in total. Those input limits still apply when the environment's holding limit is larger. Split a larger migration into appropriately sized inputs and inspect each plan and run; a holding limit is not permission to submit an oversized bundle.

The broker also has operational snapshot capacity bounds. They protect serving capacity and are separate from these product limits. A capacity failure does not grant additional import quota or justify treating an imported sign-in as a native one.

The [WorkOS compatibility support policy](/migrate/compat-workos/) is another separate concern. Its support window and published pricing are policy; this page describes the implemented create-only profile limits, not compatibility billing or expiry enforcement.
