Select Data
Choose the supported data types to include in the active migration, understand path-specific availability, and review required dependencies.
Select Data
Section titled “Select Data”Select Data defines which supported data types participate in the migration. The available choices are determined by the active Source-to-Target path, so a data type can appear for one platform combination and be absent for another.
Available data types
Section titled “Available data types”The table separates path availability from the additional Demo Migration limit. Path-specific means the data type is available only when both platforms and the active migration path support it.
| Data type | Full Migration | Demo Migration |
|---|---|---|
| Taxes | Path-specific | Available when supported by the path |
| Manufacturers | Path-specific | Available when supported by the path |
| Categories | Path-specific | Available when supported by the path |
| Products | Path-specific | Available when supported by the path |
| Customers | Path-specific | Available when supported by the path |
| Orders | Path-specific | Available when supported by the path |
| Reviews | Path-specific | Not included |
| Coupons | Path-specific | Not included |
| CMS Pages | Path-specific | Available when supported by the path |
| Blog Posts | Path-specific | Available when supported by the path |
Choose the migration scope
Section titled “Choose the migration scope”- Review the data types shown for the active migration and any dependency notice associated with the selection.
- Select the data types required for the migration. Use Select All when every available data type is required, or Clear All to reset the selection.
- Review any data type selected automatically because another selected type depends on it.
- Click Next after the scope matches the intended migration.
Include or exclude whole data types
Section titled “Include or exclude whole data types”Use Select Data when the requirement is to include or exclude an entire supported data type. For example, if Orders are not part of the approved scope, leave Orders unselected. Do not create a Data Filter merely to exclude every record of a data type.
A selected data type can require another supported data type as a dependency. If Next-Cart selects a dependency automatically, review why it is required before changing the scope. The final selection should preserve the relationships required by the data types that remain in scope.
Use Data Filter only when the data type is included but some records inside it must be selected by supported field-level conditions.
What to verify
Section titled “What to verify”Before continuing, confirm that every required data type is selected and that automatically selected dependencies are intentional. A data type appearing in Select Data confirms path-level availability; it does not mean every source field or relationship has a direct target equivalent.
Next Steps
Section titled “Next Steps”Continue to Additional Options to review optional migration behaviors. To revise the platform connection instead, use Back to Connect.