Purpose of data transfer profiles in mass changes

Data transfer gathers the implemented import, export and base profiles into one workspace. The profile defines the data area, direction, file format, execution method, parameters and processing rules.

Use export for data review or further processing and import for controlled mass changes. Always read the specific description and instructions for the selected profile: different imports do not handle errors, missing rows, or deletions in the same way.

Data transfer: import and export data using profiles

Data transfer imports and exports data with profiles in the different areas of products, categories, attributes, manufacturers, media, customers, prices, and orders. Each card applies to one limited function, such as Export Products, Import Categories, or Import Customer Price List. In addition to the name and description, the card shows the subject area, direction, file format, and execution method.

The workspace address is /data-exchange . Profiles contains running profiles and History opens at /data-exchange/history .

The current profile grid only shows profiles in the Implemented state. Unavailable profiles are filtered out before drawing cards, even though the data model is aware of this state.

Narrow down the profile list

Narrow the profile list by direction, subject area, name, and hiding status.

1. Open Data transfer > Profiles .
2. Select Import or Export .
3. If necessary, narrow the Subject Area .
4. Type part of the profile name in the search field.
5. Enable Show Hidden if you are looking for a previously hidden profile.

The restrictions are saved in the page address. Clear them if the implemented profile you expect is not displayed.

An import template can appear as a profile for the import direction, even though its function is to load a file. The name of the card's main function indicates whether to open the import, run the profile, or load the template.

Check the profile card

Before driving, check the profile card for at least the subject area, direction, file format, and execution method.

• Importing may change store information.
• Export produces a file or other export result without changing the import target.
• Synchronous execution is processed upon request.
• The background job is queued and monitored from the runtime or history.
• The file format can be, for example, CSV or XLSX, depending on the profile definition.

The card description tells you the exact data content of the profile. Don't just assume from the subject area which columns will be exported or what the import will replace.

Open the editor to display the profile details and history. Run Profile , Import, or Load Template will launch a workflow based on the profile type.

Perform export

Complete the export by filling in the profile's own parameters, previewing, and starting the run.

1. Select Run Profile for the export profile .
2. Read the profile-specific instructions.
3. Fill in the parameters that appear, such as date range or status code.
4. Select Preview .
5. Check the number of lines in the preview.
6. Select Run .
7. Track your ride in the box or on the History page.
8. Download the completed file when the successful run has a download link.

Preview does not load the final export file. It displays a preview rowset returned by the implementation and helps you check the cropping before running.

The background job status is updated in the run box approximately every 1.5 seconds as long as the run is Queued or Running. You can close the box and continue monitoring from History.

Download import template

Load an import template from a profile whose main action is Load Template .

1. Select the correct import topic.
2. Look for a profile whose name or description indicates it is a base.
3. Select Load template .
4. Save the file and keep its column headings.

The base profile produces an empty file with the expected columns. It does not contain any current store data. If you need existing values as a starting point for editing, run the corresponding export profile.

Not all import profiles have a separate base profile. Check the profile's own description and the column instructions in the import view.

Preview and import

Preview and complete the import in the selected profile's own import view.

1. Select the import action for the implemented import profile.
2. Upload the CSV file expected by the profile.
3. Review the preview summary, line-by-line errors, and planned changes.
4. Repair the file if preview prevents execution.
5. Only confirm the performance once the impact is understood.
6. Check the run result and the number of rows processed in History.

Don't assume that all imports are "all or nothing" across the entire file. Atomicity depends on the profile implementation: some write a single transaction, some process entities separately, and for example, order status imports may accept rows individually. Profile-specific preview and reporting are crucial.

The meaning of missing rows also varies. Some imports are incremental, some replace the entire membership, and deletions may require an exact CONFIRM value or other profile-specific confirmation.

Edit profile name and description

Edit the profile name and description on the Basics tab in the profile editor.

1. Select Open Editor from the card.
2. Open Basic information.
3. Change the Finnish or English name and description.
4. Exit the field and wait for the autosave.

Code, subject area, direction, origin, file format, execution mode, execution method, and possible processor key are locked data. Changing the name or description does not change the import or export processing logic.

The Edit card shortcut uses a separate save form, while the actual editor auto-save localized text. Please check the save notification before exiting.

Clone, hide or restore a profile

Clone, hide, or restore a profile from the card's Actions menu.

Cloning requires a unique profile key. The key uses lowercase letters, numbers, and dashes, and cannot end with the reserved -default suffix. Finnish and English name overrides are either both provided or both left blank.

Hiding displays a confirmation window and removes the profile from the default list. It does not delete the profile or history. Enable Show Hidden and select Restore to return the profile to the default list.

Hiding does not prevent the technical use of the profile elsewhere. Use it to tidy up your workspace, not as a permission or security boundary.

Check your driving history

Check your driving history on the History page or on the History tab in the individual profile editor.

The history shows, for example, the type of run, its status, creation, start, and completion times, request ID, requesting administrator, number of rows processed, and a failure summary. The statuses are Queued , Running , Succeeded , Failed , and Canceled .

Limit history by status and profile. The Load More function will bring up the following rows.

Download is only available for a successful run with a saved result file. A successful status alone does not guarantee a download link for a writeable import, for example.

Impact on online shopping

The impact of data transfer on the online store depends on the profile performed. Export reads data and produces a result, but import can change products, categories, attributes, customers, prices, media, or orders.

Don't expect every import to appear immediately in all storefront views. The impact depends on the write path, caches, indexing, and data used by the theme. Check the profile report and target data in the admin and, if necessary, in the online store.

Before performing a destructive or bulk import, perform an appropriate export or other approved backup. However, an export is not automatically a complete return package; verify that it includes all fields changed by the import.

Good to know

Good to know about Data Transfer profiles and times:

• The workspace currently only shows Completed profiles.
• The profile description and instructions determine the actual content.
• Previewing does not mean that all imports are atomic across the entire file.
• The meaning of the missing line and deletion varies by profile.
• The base is an empty column structure; the export contains the current data.
• The profile name and description are editable, technical fields are locked.
• Hiding preserves your profile and history.
• The history shows runs and offers download only when the result file exists.