Upload Source Data Files
Upload only the entities and filenames listed under Supported Files for the selected File Upload Source Platform, and verify that Next-Cart recognizes the source data.
Upload Source Data Files
Section titled “Upload Source Data Files”Use File Upload only when it is available for the selected Source Platform and, where applicable, the selected connection method or edition. The Supported Files section in the Connect Stores step defines the standard data entities and expected filenames eligible for that Source setup. Upload the listed files that correspond to the data included in the migration scope. Obtain them through the platform-specific procedure: some exports require Next-Cart technician assistance, including Weebly Reviews. An accepted filename does not establish that a native export button exists.
Upload the source files
Section titled “Upload the source files”- In the Connect Stores step, confirm that the selected Source setup uses File Upload and review its Supported Files list.
- Prepare only the required listed files using the matching Source Data Export Guide. Preserve the required filenames and structure.
- Upload the prepared files for the active Source setup. Do not add unlisted entity files or rename another platform’s export to imitate a supported filename.
- Confirm that Next-Cart accepts the required files and recognizes Source records. An unexpected 0/0 indicates that the file content or structure still needs correction.
- Confirm the Target setup, then click Continue to Configuration when both sides are ready.
Open the correct preparation guide
Section titled “Open the correct preparation guide”Preserve the required file structure
Section titled “Preserve the required file structure”Standard File Upload is structure-specific: the file must match the selected Source setup or the applicable Next-Cart template. A non-standard file or another structure is not treated as universally compatible.
When the supplied data files do not match a standard File Upload structure, provide the files and the required migration outcome through Prepare Custom Migration Requirements. Next-Cart technicians can create a project-specific file-processing solution around the supplied files when that work is accepted in the Custom Migration scope. The supported format, structure, entities, relationships, and transformation rules are defined by that project scope rather than by a blanket any-format or any-structure rule.
Before upload:
- use the exact files listed under Supported Files for the selected Source setup;
- preserve the required filename, fields, identifiers, encoding, hierarchy, and relationships;
- do not rename a different export to mimic an expected filename;
- do not convert one platform’s export into another platform’s file structure unless the migration has an approved Custom scope for that conversion; and
- keep a protected working copy until migration validation is complete.
CSV, XLS, and XML
Section titled “CSV, XLS, and XML”CSV, XLS, and XML are Custom Migration Source Platform selections with a Products-only included workflow.
| Source Platform | Supported entity | Expected filename | Guide |
|---|---|---|---|
| CSV | Product | products.csv | Prepare CSV Source Data Files |
| XLS | Product | products.xls | Prepare XLS Source Data Files |
| XML | Product | products.xml | Prepare XML Source Data Files |
The preparation guides include downloadable Product samples. Use the sample for the selected CSV, XLS, or XML Source option; keep a native platform export in its own required structure.
A structurally invalid Product file can still be accepted as an upload while the migration later reports 0/0, meaning no Source Product records were recognized and no Product records were migrated. Correct the structure against the corresponding file guide before retrying.
Verify upload readiness
Section titled “Verify upload readiness”| Check | Pass condition |
|---|---|
| Source setup | The selected platform, method, and edition match the file workflow being used. |
| Supported Files | Every uploaded entity and filename appears in the Supported Files list for the selected Source setup. The migration scope determines which eligible listed files need to be provided. |
| Structure | Each file preserves the expected platform or Next-Cart template structure. |
| Upload | Next-Cart accepts the required files. |
| Record recognition | Migration progress shows recognized Source records rather than an unexpected 0/0. |
| Target setup | The Target connection is ready before continuing to Configuration. |
Store URL behavior
Section titled “Store URL behavior”File Upload does not automatically mean that the Source has no Store URL. Wix File Upload and Lightspeed Retail (S-Series), for example, still expose a Source Store URL field. CSV, XLS, and XML do not.
For paid migrations, URL locking follows the actual URL fields in the selected setup. Review Store URL Locking and Store Identity before advancing to Configuration.
If the file cannot be used
Section titled “If the file cannot be used”| Problem | Corrective action |
|---|---|
| A file for an intended supported entity is missing | Follow the matching Source Data Export guide, including any required technician-assisted export. Do not infer an export method from the expected filename. |
| Filename or structure does not match | Re-export or rebuild from the correct platform/template source. If a standard structure cannot be produced, provide the source files and required outcome for an approved Custom Migration file-processing solution. Do not fix the problem by changing only the extension or inventing columns. |
| CSV, XLS, or XML reports 0/0 | Correct the Products file against its dedicated template guide, re-upload it, and confirm that Source Product records are recognized. |
| Another entity is required | Add the data type and its handling to the approved Custom Migration scope. |
| Connect Stores assigns another connection method | Stop the File Upload workflow and follow the method displayed for that selection. |
If the required standard file cannot be produced or accepted, use Troubleshoot Connection Setup.
Next Steps
Section titled “Next Steps”After the required Source files and Target setup are ready, click Continue to Configuration. If you need to verify Target access first, use Test Platform Connections.