Entity Points Issues

Entity Points Issues

Restore sufficient and correctly understood Entity Points coverage before processing remaining eligible records. Use this page when the Migration step reports insufficient capacity, Statistics shows an unexpected usage change, the purchased plan appears incorrect, or required records remain unprocessed after available capacity is reached.

Entity Points are a service-coverage measure, not a record-selection control. Diagnose the purchased service, migration path, successful newly eligible records, earlier counted records, source-data window, and displayed plan evidence before changing scope or starting another migration activity.

Purchase quantities do not filter migration records

Data estimates entered during purchase help calculate Entity Points coverage. They do not automatically limit which source records are read or migrated. Use supported data-type selection, Data Filter when purchased, or approved Custom Service when the scope must exclude particular records.

Identify the observable problem

Observable problem	What it usually means
Migration cannot start or continue because capacity is insufficient	The purchased Entity Points Plan may not cover the remaining newly eligible counted records.
Some eligible records are processed and remaining records stop	Available capacity may have been exhausted during the activity, or another processing issue may be affecting the remaining scope.
Entity Points usage is higher than expected	The source scope may contain more newly eligible counted records than estimated, or the reviewed activity, service, path, or source-data window may be different from the one expected.
Records processed in another activity appear to consume points again	The records may be new to this purchased service or migration path, may not have succeeded previously, or the displayed evidence may require support review.
The number entered during purchase did not restrict migrated records	This is expected. Purchase quantities determine coverage planning, not automatic record filtering.
Support or relationship data appears in the result	Supporting data can be processed to preserve relationships and does not consume Entity Points independently merely because it accompanies counted records.
The plan shown under My Migrations does not match the completed order	The wrong account, order, service, or migration path may be open, or order processing may require review.
Usage changes do not align with Success, Failed, or Skipped results	The comparison may use the wrong activity window, include records already counted elsewhere, or require internal reconciliation.

Preserve the evidence before changing scope

Record:

• the signed-in account and order reference;
• the purchased service and fixed Source Platform to Target Platform path;
• the Entity Points Plan shown under Migrations → My Migrations;
• the values shown under Statistics, including plan, usage, and Upgrade Your Migration where available;
• the relevant History entry and activity time;
• the migration action used;
• whether Continue the previous migration or Migrate only newly added entities was enabled;
• the intended source-data window;
• selected data types and applicable Data Filter behavior;
• Success, Failed, and Skipped counts;
• representative source and target identifiers for newly processed and earlier processed records;
• points or capacity shown before and after the activity when available.

Do not include passwords, private keys, complete payment details, private access tokens, or unnecessary personal data.

Diagnose the Entity Points result

1. Confirm the account, order, service, and migration path

   Open Account → Migrations → My Migrations and identify the intended purchased service. Confirm that the migration path, Service, Entity Points, Service Duration, and Status match the completed order.

2. Review Statistics and History

   Open Statistics to review the displayed plan, usage, progress, linked order, and Upgrade Your Migration information. Open History to identify the exact migration activity and account context associated with the change.

3. Define the activity’s source-data window

   Record the migration action and review Continue the previous migration and Migrate only newly added entities separately. Confirm whether the activity read the full selected scope, resumed interrupted processing, or read only records added after the last successful run.

4. Reconcile successful newly eligible records

   Compare the usage change with records that became eligible and migrated successfully for the first time under the same purchased service and migration path. Use representative identifiers rather than relying only on aggregate counts.

5. Separate earlier counted records

   Identify records that had already been counted under the same purchased service and migration path. They should not consume Entity Points again merely because another supported migration activity processes them.

6. Separate Failed, Skipped, and support data

   Review records that did not migrate successfully and data processed to preserve relationships. Do not assume every processed row, selected data type, or supporting record consumes Entity Points in the same way.

7. Check whether the intended scope exceeded the plan

   Compare the purchased coverage with the actual newly eligible counted scope. If the business intended a narrower record-level scope, confirm whether Data Filter was purchased and configured or whether approved Custom Service was required.

8. Classify the issue before another activity

   Determine whether the result is expected capacity exhaustion, an inaccurate purchase estimate, a scope or source-window mismatch, a plan or order mismatch, a suspected repeat count, or an unexplained usage discrepancy.

9. Apply the appropriate correction

   Upgrade coverage, correct future scope, resolve the order or service mismatch, or submit a ticket with the preserved evidence. Choose a later migration action only after the current target state and remaining source scope are understood.

Choose the correction by cause

Confirmed cause	Safest corrective path
Actual newly eligible counted scope exceeds the purchased plan	Use Statistics → Upgrade Your Migration where available and complete the approved upgrade before processing remaining eligible records.
Purchase estimate was lower than the source-store reality	Update the capacity plan. Do not expect the original entered quantity to stop migration at that record count.
The business needs only certain records within a selected data type	Use Data Filter when purchased and supported, or define approved Custom Service requirements. Data-type selection alone cannot filter individual records.
The wrong account, order, service, or migration path is open	Stop migration work, identify the correct purchase, and use Orders and Migrations to reconcile access.
A later activity includes new eligible records	Confirm that those records had not successfully migrated before under the same purchased service and path. The new successful records can consume Entity Points.
Previously counted records appear to consume again	Preserve before-and-after usage, stable record identifiers, the service and path, History entries, action, source-reading options, and Success results. Submit a ticket before another activity if the evidence remains inconsistent.
Remaining records were not processed after capacity was exhausted	Complete the required plan upgrade, confirm the current target state and remaining source-data window, then use Compare Migration Action Options to choose the correct later action.
Failed or Skipped records are being treated as the entire explanation	Review their reasons separately. Capacity and record-processing failures can coexist and require different corrections.
Supporting data is mistaken for independently counted records	Confirm whether the records were processed to preserve required relationships. Do not infer consumption from presence alone.
The displayed plan or usage conflicts with the linked order	Preserve the order, My Migrations, Statistics, and History evidence and submit a ticket for account or purchase reconciliation.

Do not manually import the remaining records to avoid an upgrade

Manual imports can break source-to-target identity, relationships, later migration actions, and validation evidence. Resolve plan coverage and the appropriate migration path before processing the remaining scope.

Verify the correction

Verification area	Pass condition
Correct purchase	The signed-in account, order, purchased service, and migration path all refer to the intended project.
Plan coverage	The Entity Points Plan covers the approved remaining newly eligible counted scope.
Usage reconciliation	The usage change can be explained by representative records that migrated successfully for the first time under the same service and path.
Earlier records	Previously counted records are distinguished from newly eligible records and do not show an unexplained repeat-consumption pattern.
Source-data window	The migration action and Source Platform Options match the intended full, resumed, or newly-added-only scope.
Processing evidence	Success, Failed, and Skipped results are recorded and investigated separately from capacity.
Scope control	Any required record-level limitation uses a supported purchased filter or approved Custom Service rather than purchase quantities.
Remaining records	Required remaining records can be processed through an approved later action after coverage and target state are confirmed.

Evidence to collect for support

When the issue remains unresolved, provide:

• order reference and purchased service;
• Source Platform and Target Platform;
• migration path and target environment;
• Entity Points Plan and displayed usage;
• screenshots of My Migrations, Statistics, and the relevant History entry with sensitive information masked;
• activity date, migration action, and Source Platform Options;
• source-data window and selected data types;
• Success, Failed, and Skipped counts;
• points or capacity before and after the activity where available;
• representative source and target identifiers for newly successful, earlier counted, Failed, and Skipped records;
• expected result, actual result, and corrections already tested.

Do not send passwords, full secret keys, payment-card data, complete billing records, or unnecessary customer information.

When to escalate

Use Tickets when:

• the linked order and displayed Entity Points Plan do not match;
• previously counted records under the same purchased service and migration path appear to consume Entity Points again;
• the usage change cannot be reconciled with successful newly eligible records;
• capacity remains unavailable after an approved upgrade is completed;
• a supported activity stops despite confirmed sufficient coverage;
• Statistics, History, or migration results show conflicting information;
• the correction requires account, order, plan, or internal usage reconciliation;
• another migration activity would risk duplicates, replacement, or loss of protected target data.

Prevent Entity Points issues

• estimate counted data from the current source store rather than an old export or catalog snapshot;
• include expected growth and newly added records in capacity planning;
• confirm the purchased service and migration path before every activity;
• review Statistics and History before choosing a later migration action;
• document the intended source-data window and Source Platform Options;
• use supported scope controls instead of treating purchase quantities as filters;
• compare usage with successful newly eligible records after each meaningful activity;
• preserve representative identifiers and before-and-after evidence;
• resolve unexplained usage before additional migration activity.

Next step

For complete definitions and plan boundaries, use Entity Points and Entity Points Plans and Service Pricing.

After capacity and the current target state are confirmed, use Compare Migration Action Options to select the appropriate next activity. When records remain absent for reasons other than capacity, continue with Missing Data.