Imports
Learn more about available import types the best practices on the import process.
Best Practices for Large-Scale Imports in Open Loyalty
When migrating data to Open Loyalty, careful planning and execution are essential to ensure accuracy and maintain the integrity of your loyalty program. This article focuses on the important considerations and recommended practices for large-scale imports.
1. Start with Member Data
The first step in any large import process is to migrate your member data. This step establishes member profiles in the system and provides the foundation for linking other data, such as transactions and unit transfers.
Why Start with Members?
Members are the core of your loyalty program.
Other imports, such as transactions or point transfers, require accurate member IDs to associate the data correctly.
Key Tip: If your focus is only on getting started quickly, migrating only member data is often sufficient. Transactions, unit transfers, and other optional imports can be added later.
2. Map Member IDs
After importing members, it is crucial to map their IDs accurately to ensure seamless data association for subsequent imports.
What is Mapping? Mapping ensures that every unit transfer corresponds to the correct member profile.
Risks of Skipping This Step:
Incorrect data association.
Discrepancies in member balances and loyalty program metrics.
You can add the following events using the external identifier (such as email, phone number, or loyalty card number):
Transactions
Custom Events
At the moment, the following events require member ID generated in Open Loyalty:
Unit Transfers
3. Import Unit Transfers
Once member IDs are mapped, proceed to import unit transfers. This step updates member balances with points (or other units) they’ve earned or spent.
Sequence Matters: Unit transfers rely on existing member IDs, so performing this step earlier could lead to errors or unlinked data.
4. Plan for Data Integrity
Adhering to the correct sequence—members first, followed by mapping, then transactions and unit transfers—ensures data integrity and avoids inconsistencies in your loyalty program.
5. Optional Imports
Remember that while transactions and unit transfers add value to your loyalty program, they are not mandatory to get started. Focus on migrating your core data (members) first and introduce other imports as your program scales.
The complete list of available import files can be found in the article below:
Enhanced Considerations for Large Databases
Test Migration on a Small Dataset First
Before migrating your entire database, conduct a test migration using a small subset of data in your stage environment.
Benefits:
Identifies potential errors early.
Ensures your data format and mapping are correct.
Validates system behavior under controlled conditions.
Reserve Adequate Time for Each Import Type
For large databases, allocate sufficient time for each type of data import.
For example:
A day for importing members.
Another day for transactions.
A separate day for unit transfers.
This approach minimizes pressure, reduces the risk of errors, and allows time to troubleshoot any issues.
Communicate with Open Loyalty Support
Inform the Open Loyalty team of your migration schedule in advance. This way, we can allocate additional
Last updated