Emarsys Loyalty provides an option to migrate the contacts from your existing loyalty program to the new one in the Loyalty add-on.
The following parameters can be migrated to the new program:
- Member status (tier)
- Member points, such as:
- Status points (points to advance to the next tier)
- Balance points (points to redeem)
On the day of migration, send a .csv file with below mentioned columns to your Implementation Consultant so the Loyalty team can migrate your contacts and their data.
The Loyalty system treats migrated members as new members. The migration day will be considered as the joining date.
This affects the following parameters:
- Yearly calculation for tiers - if you set the yearly calculation as 12 months from the date of joining, the next calculation will be in 12 months from migration day. In such a scenario, the members will stay in that tier for at least 12 months.
We are not migrating the join date of the previous program.
- Points expiration - The validity start date for all points migrated will be the migration date. Once the points are migrated, their expiration date will be adjusted to the newly defined plan settings.
We are not migrating the previous points expiration dates.
CSV file specifications
-
This
.csvfile has to be sent with all contacts to be migrated. - Do not use decimal separators (comma, dot) in your numbers:
Do not send 1.000 or 1,000. Do send 1000.
The .csv file must contain the following columns:
-
userid- The unique identifier for your contact, the same identifier you used in the uploaded sales data. -
tierName- The name of the tier to be assigned to your contact. Without a tier name, the contact will be placed automatically in the bottom tier (tier 1).
The tier name has to be written exactly how it is defined in the Emarsys Loyalty plan settings!
If the tierName field stays blank, the Loyalty system will distribute members among tiers based on their existing status points and the new tier requirements. For example, if a member has enough points for Silver, he will be added to this tier including the existing status points.
-
statusPoints(optional): The amount of status points to migrate that this member will see in the wallet.
For example, this customer starts the new plan as a silver member with 540 status points (points from previous plan):
If you keep the statusPoints field blank, the status points will be 0 and the member will be distributed into the tier defined in column: tierName.
-
pointsToSpend(optional): The amount of points for spending (to redeem). The validity period of the points will start from the moment the contact is migrated. Alternatively, you can decide that the contacts will start without points to spend. -
shouldJoin: Set the value for this column to “TRUE” for all contacts. -
planId: In case you want a multiplan setup, add theplanIdfor each contact so the Loyalty system can assign them to the relevant plan. TheplanIdwill be the same as the identifier defined in the Onboarding screen in the suite. -
shouldReward: This parameter is used by migration scenarios. When set toTRUE, marked contacts receive the default join reward after migrated into the Loyalty program. Contact marked withFALSEdo not count as new joiners, thus they do not receive join rewards.
