Run a Full Migration

Run a Full Migration

Run the first complete migration after the store connections, configuration, target impact, Entity Points capacity, and validation plan have passed final review.

Before you start

• The purchased migration service is Active.
• Both store connections pass verification.
• The final configuration review has a Go decision.
• The target store is in the approved state for migration.
• Apps or automation that could create conflicting records are controlled.
• Recovery evidence exists before any destructive target action.
• The validation reviewer has a representative sample list and pass conditions.

Start the Full Migration

1. Open My Migrations

   Go to Account -> Migrations -> My Migrations and select Start for the intended Active service.

2. Confirm Connect Stores

   Verify the source store and target store shown for the migration path. Correct any expired credential, inaccessible file, removed KitConnect setup, or changed URL before continuing.

3. Confirm Configuration

   Review the completed Data, Options, Mapping, Add-ons, and Custom stages that apply to the service.

   Return to configuration if any setting differs from the approved review.

4. Open the Migration step

   Confirm the Source Platform, Target Platform, Entity Points usage, selected data types, and readiness status.

5. Select a Run Mode

   Choose Run in Browser when the tab can remain open for the entire migration. Closing or navigating away from the page can pause processing in this mode.

   Choose Run in Background when processing should continue on Next-Cart servers after the browser is closed or the computer is turned off.

6. Review deletion warnings

   If target-data clearing is enabled, confirm the listed data types and the permanent deletion warning. Do not continue if the displayed scope differs from the approved target impact.

7. Start migration processing

   Select Start Migration and confirm that the selected data types enter an active or queued state.

8. Monitor progress

   Track progress, successful records, failed records, and skipped records for each data type.

   Keep source and target access stable while processing continues.

9. Respond to actionable failures

   Review the affected data type and record counts. Correct connection or source-access problems only when the interface allows a safe recovery. Avoid changing the approved configuration during active processing.

10. Confirm completion

    Verify that every selected data type reaches a completed or reviewed final state. Download the migration log when available and record failed or skipped items for validation.

Understand migration progress

Status area	What to check
Progress	Processed records compared with the expected total for each data type.
Success	Records completed successfully.
Failed	Records that require investigation or corrective action.
Skipped	Records intentionally or technically omitted; each reason must be reviewed.
Entity Points usage	Capacity consumed by newly migrated eligible counted records.
Migration log	Detailed evidence for troubleshooting and validation where available.

The normal dependency sequence is:

Taxes → Manufacturers → Categories → Products → Customers → Orders → Reviews → Coupons → CMS Pages → Blog Posts

In this sequence, Pages refers to CMS Page records. The visible progress list can differ when a data type is unavailable or excluded for the migration path.

Entity Points behavior

New eligible Products, Customers, Orders, and Blog Posts consume Entity Points when they migrate successfully for the first time. Previously counted records do not consume Entity Points again merely because another migration activity processes them. Taxes, Manufacturers, and Categories are support data and do not consume Entity Points.

Do not use record quantities as filters

Quantities entered during purchase determine plan coverage. They do not restrict which records are read. Use data selection, a purchased Data Filter Add-on, or Custom Service when the migration scope must be limited.

Expected result

The Migration step shows a final state for every selected data type. Successful records are available on the target store, and failed or skipped records are documented for validation or troubleshooting.

Verify completion

Check	Pass condition
Correct service	The activity belongs to the intended migration path and purchased service.
Run Mode	Processing followed the selected browser or background behavior.
Data types	Every selected data type has a final status.
Counts	Success, failed, and skipped totals are recorded.
Entity Points	Usage aligns with newly migrated eligible records.
Target protection	No unapproved target records were deleted or replaced.
Evidence	Completion time and migration log are saved where available.

If the migration does not complete

Problem	Next action
Browser mode pauses	Reopen the activity and follow the available continuation behavior. Use background mode for future activity when appropriate.
A connection becomes unavailable	Restore the required access and verify both stores before resuming.
A data type fails	Capture the data type, counts, record examples, and migration log details.
Records are skipped unexpectedly	Review filters, dependencies, platform constraints, and source data.
Entity Points capacity is exhausted	Upgrade the Entity Points Plan before processing remaining eligible records.
Target data was affected unexpectedly	Stop further activity, preserve evidence, use the recovery plan, and contact support.

Next step

Continue to the complete target-store validation process under Validate and Launch Your Target Store.