Skip to content
Back to Site

Entity Points

Plan and verify capacity correctly by separating counted eligible records from migration scope, filtering, repeat processing, and relationship support data.

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. For conceptual planning context, see Entity Points in the Learning Center.

Each purchased migration service has an Entity Points Plan tied to its fixed Source Platform → Target Platform migration path.

Each counted data type has a specific locked weight. The weight determines how many Entity Points one successfully migrated record consumes.

Counted data typeWeight
Products1 point per Product
Customers0.5 point per Customer
Orders0.8 point per Order
Blog Posts0.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.

For example:

CalculationEntity Points
1,000 Products × 11,000
2,000 Orders × 0.81,600
500 Customers × 0.5250
Total2,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”

Calculate capacity from the counted records that are expected to participate in the approved migration scope:

  1. estimate the number of Products, Customers, Orders, and Blog Posts that are in scope;
  2. multiply each estimate by its locked weight from the table above;
  3. add the four weighted results to obtain the estimated Entity Points requirement;
  4. add reasonable allowance for new eligible counted records expected before the final migration activity;
  5. choose an Entity Points Plan whose capacity is at or above that requirement.

For example, 1,000 Products, 2,000 Orders, and 500 Customers require 2,850 Entity Points because the calculation is 1,000 × 1 + 2,000 × 0.8 + 500 × 0.5. Categories, Reviews, Coupons, Taxes, CMS Pages, and other supporting or non-counted data types do not add separate Entity Points simply because they are included in the supported migration scope.

Use record counts and locked weights for this calculation. File size, database size, the number of selected data types, and the number of relationships are not substitutes for the Entity Points formula.

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.

Counted capacity and included migration data are separate

Section titled “Counted capacity and included migration data are separate”

Only Products, Customers, Orders, and Blog Posts are weighted Entity Points data types. Other supported migration data can still be included without becoming a separately weighted Entity Points category.

For example, an approved migration scope can include CMS Pages, Categories, Coupons, Reviews, Taxes, URL Redirects, SEO data, and meta data when those items are supported by the active migration path. Their inclusion does not add a separate Entity Points weight merely because they are migrated alongside counted records.

A Product with all of its variations counts as one Product for Entity Points. Variants do not become another weighted Entity Points type.

By default, records are migrated from the oldest or smallest ID toward the newest or largest ID. Treat that processing order separately from capacity planning: an Entity Points Plan covers eligible counted records, while selection and filtering determine which records are intended to participate in the migration activity.

Define any record-limiting requirement before the migration activity whose scope it should control. Use Data Filter when the required condition is supported. Use Custom Migration when the required rule cannot be expressed by the supported filtering model. A later capacity estimate does not retroactively redefine records already processed by an activity.

A new eligible counted record consumes Entity Points when it is first migrated successfully.

Within the same purchased Migration and fixed Migration Path, a counted record that was already migrated successfully does not consume Entity Points again merely because later supported migration activity processes it again. Only newly eligible counted records consume their Entity Points weight when they first migrate successfully.

Result or situationEntity Points behavior
A new eligible counted record reaches SuccessIt consumes points according to its locked weight.
A counted record is Failed or SkippedThat 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 pathIt does not consume points again merely because another supported migration action processes it.
Supporting relationship data is processedIt does not consume points independently merely because it supports a counted record.
A quantity is entered during CheckoutThe quantity supports calculation and plan selection; it does not become a record-level migration filter.

Entity Points are separate from the controls that define what Next-Cart reads or processes.

ControlWhat it determines
Data selectionWhich supported data types are included in Configuration.
Data FilterWhich records inside a selected data type meet configured field-level conditions for that data type.
Migration actionWhether Connect Stores uses Continue previous migration, Continue previous + reconfigure, or Start a new migration.
Continue action + Continue the previous migrationWhether a Continue action carries the most recent migration state into the current one so records not transferred in that previous state form the delta while supported relationships use the carried context.
Execution recoveryWhether an active or interrupted activity is controlled through Run Mode, Stop Migration, Resume Migration, or the documented return flow. Execution recovery does not change Entity Points eligibility by itself.
Service typeWhether the purchased service is Standard Migration, Managed Migration, or Custom Migration.
Entity Points PlanThe counted-record capacity available to the purchased migration service.

A migration action can process both newly eligible records and records already migrated successfully under the same purchased Migration and fixed Migration Path. Only newly eligible counted records consume points when they first reach Success. Reprocessing an already counted record does not consume its weight again.

LocationWhat to confirm
CheckoutEntered Products, Customers, Orders, and Blog Posts; calculated Entity Points; available plan capacity; service price; and final order summary.
My MigrationsExpand Migrations in the Dashboard, then select My Migrations to review the Entity Points coverage associated with the purchased migration service.
Statistics → Plan & ServicePlan and maximum Entity Points capacity.
Statistics → Data Migration ProgressCounted-record progress and Total Entity Points Used.
Statistics → Upgrade Your Migration → View Upgrade OptionsOpens 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.
HistoryMigration activity that can be compared with changes in usage.

When usage is unexpected, compare the migration activity, selected data scope, whether a Continue action was paired with Continue the previous migration, Success, Failed, and Skipped results, and representative source and target identifiers before starting another migration activity.

Do not confuseCorrect distinction
Entity Points and Demo limitsDemo uses separate sample limits. Demo limits do not define purchased-service Entity Points consumption.
Entity Points and selected data typesSelecting a data type does not reserve or limit it to an entered record quantity.
Entity Points Plan and service typeThe plan provides counted-record capacity; Standard Migration, Managed Migration, or Custom Migration determines service handling and pricing.
Reprocessing and recountingA supported action can process a previously counted record without consuming its points again under the same service and path.
Plan capacity and filteringCapacity covers eligible counted records; it does not automatically exclude records beyond the original estimate.