Entity Points
Plan and verify capacity correctly by separating counted eligible records from migration scope, filtering, repeat processing, and relationship support data.
Entity Points
Section titled “Entity Points”Entity Points determine the counted-record capacity available to a purchased migration service. They do not select records, define migration scope, or replace data filtering.
Each purchased migration service has an Entity Points Plan tied to its fixed Source Platform → Target Platform migration path.
Locked weights
Section titled “Locked weights”Each counted data type has a specific locked weight. The weight determines how many Entity Points one successfully migrated record consumes.
| Counted data type | Weight |
|---|---|
| Products | 1 point per Product |
| Customers | 0.5 point per Customer |
| Orders | 0.8 point per Order |
| Blog Posts | 0.6 point per Blog Post |
These weights calculate Entity Points capacity and usage. They remain locked for the migration and do not represent every data type that may be available for the selected migration path.
Supporting data required to preserve relationships does not consume Entity Points independently merely because it accompanies a counted record.
Calculation example
Section titled “Calculation example”A migration scope containing:
- 1,000 Products;
- 2,000 Orders;
- 500 Customers;
requires 2,850 Entity Points:
| Calculation | Entity Points |
|---|---|
| 1,000 Products × 1 | 1,000 |
| 2,000 Orders × 0.8 | 1,600 |
| 500 Customers × 0.5 | 250 |
| Total | 2,850 |
The selected plan should cover the calculated total plus reasonable allowance for new eligible records expected before the final migration activity.
Calculate Entity Points with locked weights
Section titled “Calculate Entity Points with locked weights”Entity Points are calculated from the counted data types using the locked weights documented on this page. Use the actual estimated record counts for the migration scope, multiply each counted data type by its weight, and total the result before choosing capacity.
Do not substitute the number of data types, file size, database size, or any retired capacity formula for the Entity Points calculation.
Purchase estimates do not define migration scope
Section titled “Purchase estimates do not define migration scope”The quantities entered during purchase are used to calculate required capacity. They do not automatically select, filter, or exclude records during migration.
Migration scope is controlled separately through Select Data, supported filtering, applicable Add-ons, and approved Custom requirements. If the final number of eligible counted records is higher than estimated, additional Entity Points capacity may be required before the intended scope can finish processing.
When Entity Points are consumed
Section titled “When Entity Points are consumed”A new eligible counted record consumes Entity Points when it is first migrated successfully.
| Result or situation | Entity Points behavior |
|---|---|
| A new eligible counted record reaches Success | It consumes points according to its locked weight. |
| A counted record is Failed or Skipped | That result does not establish successful consumption. Correct the cause and verify the later result. |
| A previously counted record is processed again under the same purchased service and migration path | It does not consume points again merely because another supported migration action processes it. |
| Supporting relationship data is processed | It does not consume points independently merely because it supports a counted record. |
| A quantity is entered during Checkout | The quantity supports calculation and plan selection; it does not become a record-level migration filter. |
Entity Points and migration controls
Section titled “Entity Points and migration controls”Entity Points are separate from the controls that define what Next-Cart reads or processes.
| Control | What it determines |
|---|---|
| Data selection | Which supported data types are included in Configuration. |
| Data Filter | Which records inside a selected data type meet configured field-level conditions for that data type. |
| Migration action | Whether to continue with the last used configuration, continue with a new configuration, or perform a new migration. |
| Continue the previous migration | Whether interrupted processing resumes from the point where it stopped, when available. |
| Migrate only newly added entities | Whether Next-Cart reads records added since the last successful migration run, when available. |
| Service type | Whether the purchased service is Standard, Managed, or Custom. |
| Entity Points Plan | The counted-record capacity available to the purchased migration service. |
A migration action can process both newly eligible records and records already counted under the same service and path. Only newly eligible counted records consume points when they first reach Success.
Where to review Entity Points
Section titled “Where to review Entity Points”| Location | What to confirm |
|---|---|
| Checkout | Entered Products, Customers, Orders, and Blog Posts; calculated Entity Points; available plan capacity; service price; and final order summary. |
| My Migrations | Expand Migrations in the Dashboard, then select My Migrations to review the Entity Points coverage associated with the purchased migration service. |
| Statistics → Plan & Service | Plan and maximum Entity Points capacity. |
| Statistics → Data Migration Progress | Counted-record progress and Total Entity Points Used. |
| Statistics → Upgrade Your Migration → View Upgrade Option | Opens the existing migration in Checkout for a supported upward Service, Entity Points Plan, or Add-on change. Use Purchase a Migration Upgrade for the procedure. |
| History | Migration activity that can be compared with changes in usage. |
When usage is unexpected, compare the migration activity, selected source-data window, Success, Failed, and Skipped results, and representative source and target identifiers before starting another migration activity.
Common distinctions
Section titled “Common distinctions”| Do not confuse | Correct distinction |
|---|---|
| Entity Points and Demo limits | Demo uses separate sample limits. Demo limits do not define purchased-service Entity Points consumption. |
| Entity Points and selected data types | Selecting a data type does not reserve or limit it to an entered record quantity. |
| Entity Points Plan and service type | The plan provides counted-record capacity; Standard, Managed, or Custom describes service handling and pricing. |
| Reprocessing and recounting | A supported action can process a previously counted record without consuming its points again under the same service and path. |
| Plan capacity and filtering | Capacity covers eligible counted records; it does not automatically exclude records beyond the original estimate. |
Related tasks
Section titled “Related tasks”- Use Entity Points, Plans, and Service Pricing to compare plan capacities, Standard and Managed prices, and Custom Service starting prices.
- Use Purchase a Migration to calculate expected points, select Service handling and Plan capacity, and follow the correct order path.
- Use Purchase a Migration Upgrade when an existing migration needs more capacity or another supported upgrade.
- Use Migrations to review plan coverage, Statistics, History, and upgrade access.
- Use Select Data to choose supported data types.
- Use Configure Data Filter when purchased record-level filtering is required.
- Use Entity Points Issues when consumption, remaining capacity, or processing behavior is unexpected.