Continue the Migration with the Last Used Configuration

Continue the Migration with the Last Used Configuration

Continue with the exact Select Data, Additional Options, Attribute Mapping, Add-on, and Customization parameters from the most recent migration run. Continue previous migration routes directly from Connect Stores to Migration; visiting Configuration is optional.

• Use this route when the previous result remains useful and its configuration is a suitable starting point.
• Use Edit Config before starting when you need to inspect or adjust the loaded parameters.
• Demo and a paid migration that has never run cannot use this option. Follow Run a Demo or Full Migration for those workflows.

Before you start

• Open the correct Active purchased migration and confirm remaining capacity for newly eligible counted records.
• Review the previous result in the Target Store admin. Identify records and relationships to retain, correct, or replace.
• Prepare the intended source scope, target protection, and validation samples.
• Do not change connection parameters during active processing. Existing Store URL locks remain in force.

Activity Timeline records actions and operational details; it is not a saved-settings viewer. Inspect exact loaded parameters in Configuration when necessary. Target records establish the previous outcome, not every setting that produced it.

Open the purchased migration

1. In the Next-Cart Dashboard, expand Migrations and open My Migrations.
2. Locate the intended purchased migration, check its platform pair and status, and click Start.

Connect Stores

Use Connect Stores to verify the stored Source and Target details before selecting the migration action.

1. Verify the stored connection details.

   • When both Source and Target URLs are locked, Next-Cart pre-fills the connection parameters from those identities. Check that the URLs are correct; do not re-enter or replace correct values.
   • If only one URL is locked, preserve that identity and check the other side against its intended store. A pre-filled value is not, by itself, proof that its URL is locked.
   • Complete any remaining required values or accepted Source files using Connect Your Source and Target Platforms.

2. Optionally check access.

   • Test Connection is optional, not a prerequisite for the next step.
   • A failure produces a pop-up and Not connected beside the affected platform. Resolve that side using Troubleshoot Connection Setup.
   • Follow Store URL Locking and Store Identity for an identity mismatch. No migration action clears an existing lock.

3. Choose the migration action.

   In the dropdown at the bottom of Connect Stores, select Continue previous migration. Next-Cart routes you directly to Migration, with the most recent run’s configuration preloaded.

Optional Configuration review

Stay on Migration if the loaded settings remain appropriate. To inspect exact parameters or make an adjustment, click Edit Config before processing starts. This opens Configuration without requiring you to choose another migration action.

1. Select Data.

   Open Data to review Select Data. The screen shows the data types supported for the active Source-to-Target path.

   • Select each required type, or use Select All when every available type is in scope.
   • Use Clear All only to rebuild the selection. Retain required dependencies and resolve the displayed selection warnings.
   • Click Next to open Additional Options. Use Select Data for data-type and dependency details.

2. Additional Options.

   Review the displayed controls and retain correct settings. Apply only the changes required for this run.

   Additional Option	Action
   Continue the previous migration	Confirm the intended source-processing behavior before enabling this option. Keep it separate from the migration action selected in Connect Stores.
   Clear data on your Target Store before the Migration	Enable only when deleting the selected target data types is intentional and recovery is prepared; otherwise leave it off.
   Strip HTML tags from category and product names	Enable to remove HTML markup from supported Category and Product names.
   Import descriptions images to your Target Store	Enable to copy supported images referenced in descriptions to the Target Store.
   Preserve Customer IDs on your Target Store	Enable to retain supported source Customer IDs after checking for target identifier conflicts.
   Preserve Order IDs on your Target Store	Enable to retain supported source Order IDs after checking for target identifier conflicts.
   Migrate SEO URLs of categories, products, posts and pages	Enable for the supported source URL values required by the migration scope.

   Confirm that any target clearing is approved and that the selected source scope will restore the required data. Resolve uncertain source-reading behavior before enabling it. Click Next to open Attribute Mapping. See Additional Options for detailed behavior and interactions.

3. Attribute Mapping.

   Open Mapping to review Attribute Mapping. Complete the supported groups in their displayed order; the available groups vary by migration path.

   Mapping category	Action
   Site Mapping	Select the target site for each source site.
   Language Mapping	Select the corresponding target language for each required source language.
   Root Category Mapping	Select the target root category for the source catalog.
   Attribute Set Mapping	Select the compatible target attribute set for the source attributes.
   Inventory Location Mapping	Select the target stock location for each source location.
   Customer Group Mapping	Select the corresponding target group for each source Customer Group.
   Order Payment Status Mapping	Select the target payment status with the same intended historical meaning.
   Order Fulfillment Status Mapping	Select the target fulfillment status with the same intended historical meaning.

   Compare each source value with its pre-filled target selection. Keep correct matches, change incorrect matches, and review any Skip selections. Resolve missing target counterparts before continuing. Click Next when another stage follows. See Attribute Mapping for examples and detailed guidance.

4. Add-ons.

   In Add-ons, configure the purchased capabilities supported for the selected path and entities. Complete the applicable groups below.

   • Data Filter: select the entity and click Add Filter. Choose Field, Operator, and the requested Value. Use Add Rule with AND or OR for further conditions, then review the generated Expression. Use the visual builder unless you are experienced with direct expression editing.
   • Data Transformation: select the entity and click Add Rule. Choose Target Field, then Operator, and complete Value as requested by the form. Add further transformation rows with Add Rule.
   • Advanced Data Mapping: select the entity and click Add Mapping. Choose each Source Field and compatible Target Field. Use Add Rule for another field pair.
   • Advanced Database Mapping: verify platform eligibility and schema support. Select the entity, click Add Mapping, and choose Source Field and Target Field. For an approved custom destination, select New Column and enter Custom Target Field. Use Add Rule for another mapping.

   Review the top-to-bottom order of the Add-ons and the rules within each one: Data Filter -> Data Transformation -> Advanced Data Mapping -> Advanced Database Mapping. Complete or remove every unfinished rule and resolve validation errors. Click Next when Custom follows; otherwise complete the final Configuration check below. The Add-on guides contain the detailed examples, input rules, and error explanations.

5. Custom.

   When Custom is part of the purchased configuration, review the requirements included in the active migration and select the options that match the approved scope. Resolve a missing or conflicting requirement before proceeding. Use Custom for the complete procedure.

6. Finish Configuration.

   Review the selected data, enabled options, mappings, Add-on rules, and approved Customization together. Confirm target-data protection and resolve every remaining error using Review Migration Configuration.

   Click Go to Migration to complete Configuration and open Migration.

• Without edits, the next activity uses the exact parameters from the most recent run.
• After an edit, validate the revised configuration and its effects; do not describe it as unchanged reuse.
• Continue previous migration is not the Continue the previous migration option inside Additional Options. Neither the action name nor the direct route automatically means newly-added-only processing.

Migration

1. Review the Migration screen before starting.

   • Check the Source-to-Target summary, selected data types, and any warning about target-data deletion.
   • Read Entity Points Usage as cumulative usage across this purchased migration, not progress through this run.
   • To inspect or change settings before processing, click Edit Config and review the required Configuration steps before execution.

2. Choose Run Mode.

   • Run in Browser: keep this migration tab open. Closing it or navigating away pauses processing.
   • Run in Background: processing continues on Next-Cart servers after the browser closes or the computer is turned off.

3. Click Start Migration and monitor the result.

   • Review Progress, Success, Failed, and Skipped for each data type, then the Total row.
   • Keep store access available. Do not edit connection details or configuration during processing.
   • When processing finishes, use Download Migration Log and record unexplained failures or skips.

Completed means processing finished, not that every record was imported successfully. Use Start and Monitor a Migration for status, interruption, and log guidance.

Validate continued and changed results

• Compare the actual Target Store records with the intended source scope and earlier accepted result.
• Check that earlier relationships and protected records remain intact.
• When Edit Config was used, verify each changed setting’s output as well as newly processed records.
• Record failures, skipped records, and the run’s log. Use Activity Timeline for operational activity, not as proof of configuration values.

New eligible counted records consume Entity Points when first successfully migrated. Reprocessing an already counted record under the same purchased service and path does not count it again. Use Entity Points for the complete rule.

Resolve a problem

• Unexpected loaded settings: use Edit Config before starting, compare the relevant parameters, and resolve the difference.
• Wrong source scope: review the source-reading settings and filters before another activity. Do not assume the migration action selected them.
• Interrupted run: preserve the status and log, then use Migration Continuation Issues.
• Unexpected target impact: stop further activity, preserve evidence, and contact Support before replacement or clearing.

Next Steps

Continue to Validate Results After a Migration Action.