Skip to content
Back to Site

Before You Begin

Confirm account access, service details, store access, target readiness, data scope, validation owners, and security requirements before starting migration work.

A migration should not enter connection setup or configuration until the account, purchased service, access, scope, target store, validation plan, and security responsibilities are ready.

This page helps you confirm that your Next-Cart account, purchased migration service, store access, target store, data scope, validation plan, and security responsibilities are ready.

Before you begin, make sure you have:

RequirementWhat to confirm
Next-Cart account accessYou can sign in to the account that owns the order and purchased migration.
Purchased service detailsYou know the migration path, Migration Service, Add-ons, and Entity Points Plan.
Source store accessYou can access the source store or the person who owns source access is available.
Target store accessYou can access the target store and confirm it is the correct environment.
Decision ownerSomeone can approve scope, configuration choices, and acceptance criteria.
Validation ownerSomeone can review migrated data and confirm pass or fail results.
Support contactSomeone can respond to Next-Cart support questions during setup and validation.
  1. Confirm the migration path.

    Review the selected Source Platform and Target Platform in your order or under Account → Migrations → My Migrations. Do not continue if the path does not match the stores you intend to use.

  2. Review the purchased service details.

    Confirm the Migration Service, purchased Add-ons, Entity Points Plan, payment status, and service expiration.

  3. Confirm source store readiness.

    Make sure the source store is accessible and stable. Avoid major source-store updates, bulk catalog edits, database repairs, or app changes while preparing migration work.

  4. Confirm target store readiness.

    Make sure the target store is accessible and prepared for validation. Confirm baseline settings that affect validation, such as language, currency, tax mode, shipping framework, and required platform apps or modules.

  5. Identify required access owners.

    Confirm who can provide admin access, API credentials, hosting access, exported source data files, or other setup details if Next-Cart shows that they are required for your selected platforms.

  6. List the data types you need to migrate.

    Identify required data types, such as Products, Categories, Customers, Orders, Reviews, Coupons, CMS pages, and other supported data shown in the migration interface.

  7. Identify non-standard requirements.

    Document custom fields or database columns whose required handling exceeds supported mapping, third-party app or plugin data, unusual product structures, special order workflows, custom customer groups, subscription data, or any other requirement not represented by standard data selection or purchased Add-ons.

  8. Define validation ownership.

    Decide who will review migrated products, customers, orders, content, redirects, and target-store behavior. Validation should include representative records, not only record counts.

  9. Prepare security cleanup.

    Plan how temporary credentials, API tokens, social account access, hosting credentials, and KitConnect files will be revoked, rotated, or removed after migration work is complete.

AreaPrepare this informationWhy it matters
AccountAccount email, Order #, purchased migration, payment statusSupport and migration access depend on the correct account and service.
Migration pathSource Platform, Target Platform, source store URL, target store URLThe purchased service applies to the selected path.
AccessStore admin access, API credentials, hosting access, source export access, or contact ownerConnection setup depends on what Next-Cart shows for the selected platforms.
ScopeRequired data types, exclusions, filters, date ranges, and special recordsScope controls what must be migrated and validated.
Add-onsPurchased Add-ons and where they applyAdd-ons affect supported migration behavior and configuration.
Custom ServiceNon-standard data, transformations, app/plugin data, and examplesCustom Service requirements need clear examples and expected results.
Entity PointsExpected data volume and current Entity Points PlanCapacity affects whether all eligible data can be migrated under the current plan.
ValidationSample records, pass criteria, blocker definitions, launch timelineValidation determines whether migration output is acceptable.
SecurityTemporary access, cleanup owner, credential rotation planAccess must be protected during and after migration work.

After completing this checklist:

  • the correct Next-Cart account and purchased service are identified;
  • the migration path is confirmed;
  • the source store and target store are accessible;
  • the required setup owner is available;
  • the target store is ready for validation;
  • the data scope is clear enough to configure;
  • non-standard requirements are documented;
  • validation ownership and pass criteria are defined;
  • security cleanup responsibilities are known.

Before moving to connection setup, verify these items:

CheckPass condition
Account checkYou can sign in to the account that owns the order and purchased migration.
Service checkThe migration path, Migration Service, Add-ons, and Entity Points Plan match your intended work.
Source checkThe source store is accessible and contains the data you expect to migrate.
Target checkThe target store is the correct environment and can be reviewed after migration.
Access-owner checkThe right person can provide required credentials, files, or hosting access.
Scope checkRequired data types and known exclusions are documented.
Custom requirement checkNon-standard data or behavior is identified before configuration begins.
Validation checkSample records and acceptance criteria are ready.
Security checkTemporary access cleanup is planned.
IssueWhat to do
You cannot access the correct Next-Cart accountRecover account access or contact the account owner before continuing.
The migration path is wrongDo not configure migration work. Review the order or purchase the correct migration path.
Payment is incompleteComplete payment through Checkout before starting paid migration work.
The source store is unstableResolve source-store issues before connection setup. Avoid migration work during repairs or major updates.
The target store is not readyPrepare the target store enough for validation before running full migration work.
Access owner is unavailableAssign a replacement owner or delay setup until required access can be provided.
Scope is unclearUse Define Migration Scope before configuring data types or Add-ons.
Non-standard requirements are discoveredPrepare Custom Service requirements with examples and expected results.
Entity Points may be insufficientReview your Entity Points Plan and upgrade if required.
If you need toGo to
Define included data, exclusions, filters, and validation examplesDefine Migration Scope
Prepare credentials or platform accessPrepare Source and Target Store Access
Document non-standard requirementsPrepare Custom Service Requirements
Define pass and fail criteriaDefine Acceptance Criteria
Start platform setup after preparation is completeConnect Your Source and Target Platforms
Complete payment for a selected or unpaid serviceCheckout