Step 1. Choose an action
- Pick the import type — Customers.
- Pick the action:
- Edit existing — updates existing customers only. New records are not created.
- Add and edit — updates existing customers and creates new ones for rows that don’t match.
Step 2. Prepare and upload the file
-
Decide which fields to load. The full list is below.
Available fields:Each row must include at least one customer identifier: email, mobile phone, or an external identifier. Other fields are optional.
Field Description EmailEmail address IsEmailConfirmedWhether the email is confirmed MobilePhoneMobile phone IsMobilePhoneConfirmedWhether the mobile phone is confirmed DiscountCardLoyalty card number AreaCustomer’s area identifier LastNameLast name FirstNameFirst name MiddleNameMiddle name FullNameFull name SexGender BirthDateDate of birth IsSubscribedGlobal subscription flag IsSubscribedByEmailSubscription on the Email channel IsSubscribedBySms,IsSubscribedByViber,IsSubscribedByMobilePush,IsSubscribedByWebPushSubscription on other channels IsSubscribedByEmailOnNewsTopic-level subscription (one per topic/channel combination) Custom fields Any custom fields created in your project Multi-brand projects:IsSubscribed,IsSubscribedByEmail, and topic-level subscription fields subscribe the customer to the brand associated with the import’s point of contact. See How to subscribe customers to a brand below. - Export your data from the source system if needed.
-
Prepare the file. Put column headers (field names) in the first row.
- Format:
.csvor.txt - Recommended encoding: UTF-8
- Make sure values match the expected formats
- Format:
- Upload the file and click Continue.
Step 3. Configure the import
On this step, you can set additional parameters:- Data source — the integration point that indicates where the data originated. Affects how customer actions are attributed. Defaults to “Maestra Platform admin panel.”
- Point of contact — the channel or integration the action is tied to. By default, it’s derived automatically from the data source. To tie customers explicitly to a specific site or store, pick the point of contact manually.
- Segment — a static segment to add every customer from the file to. You can pick an existing segment or create a new one.
Set a point of contact
If the point of contact you need doesn’t exist yet, create it ahead of time or from the link on the import page. All rows share the same point of contact: pick the data source with that point in the settings, or set it explicitly. Rows have different points of contact: add aLastUpdatePointOfContact column to your file with the external identifier of the point of contact for each row, and enable Take value from file in the settings.
Add to a segment
Pick an existing static segment or create a new one from the import page.Use an action template
The edit action can be recorded with an action template only if you set it in the file and the template is in the “Personal action” category. Otherwise, the customer changes are saved without recording an action. If the template you need doesn’t exist yet, create it ahead of time. Specify the template in the file using theLastUpdateActionTemplate column with the template’s system name, and enable Take value from file in the settings.
Backdate the action
There’s no UI setting for action time. To backdate, add aLastUpdateDateTime column to your file with the timestamp for each row.
If you omit the column, actions are recorded with the time the import job ran.
How to subscribe customers to a brand
On multi-brand projects, the brand of the data source’s point of contact determines the brand of the subscription passed viaIsSubscribed, IsSubscribedByEmail, and IsSubscribedByEmailOnNews.
To subscribe customers to multiple brands at once, run the import once per brand.
Pick the data source you want to use
For example, to subscribe customers to the Demo brand, pick the data source for that brand’s site.
Step 4. Review and start the import
Before launching, Maestra Platform shows the first rows of your file with the mapping applied. Confirm that values land in the correct fields. If everything looks right, click Start import.Tracking the import
After it starts, the import appears in the list on the Import page. Each job shows:- Date started
- Import type
- Who started it
An edit action is recorded for a customer only if the customer was actually changed by the import and the file included a
SourceActionTemplate column with a “Personal action” template.