Check what changed after migration
Use this article after data from a previous system was migrated into your KORONA Event account. Before you resume selling, spot-check the imported records against your old system so problems surface now, not at the entrance or in the first invoice run.
Migrations are prepared together with KORONA Event. Ask your migration contact for the agreed import scope — typically customers and existing tickets or passes — and use that list to decide which checks below apply.
Before you start
- You need back-office access to orders, customers, and attendees.
- Keep the old system or an export from it available for comparison.
- Pick 5 to 10 known records per imported data type to spot-check, including long-standing customers and tickets or passes with different validity periods.
1. Check imported customers
Open Sales > Customers. Spot-check your sample customers: name, email, and address. Imported records can carry the identifier from the previous system in the External ref. field, which is visible in the customer list and on the customer record — use it to match records against your old system.
2. Check tickets and attendees
Open Sales > Attendees and open a sample attendee. In the ticket section, imported tickets are labelled with their origin, for example Legacy ticket, so you can tell migrated tickets from tickets sold in KORONA Event. Confirm the ticket is active and valid for the intended event or period.
3. Check events and prices
Open Services > Events and review the events you will sell next. On each event, check the Prices tab: price categories, synchronized products and their displayed customer prices, and quantity limits must match the intended setup, and each price must be visible at the intended POSs.
4. Check the shop state
Open the public shop URL. Confirm that only the intended offers are visible, that nothing carries a leftover Hide from shop setting, and that a full test checkout works. Follow Test the customer checkout.
5. Check integrations
If your account uses connected systems such as KORONA.entry or KORONA.studio, open Admin > Integrations and confirm each integration is configured and shows a recent successful synchronization where the page displays one.
Expected result
Your sample customers and tickets or passes match the agreed migration scope, external references let you trace records back, upcoming events have correct prices, the shop sells only what it should, and connected systems are in sync. Report any mismatch to your migration contact with the affected record and its external reference.
Troubleshooting
| Problem | What to check |
|---|---|
| A known record cannot be found | The global Search box with the old system's number; whether that data type was part of the migration. |
| A historical order is missing | Expected behavior; orders are not imported. Search the previous system or the retained export. |
| An imported ticket does not scan | Whether the ticket is active and valid, and whether the entry system integration is connected and synchronized. |
| Duplicate customers appear | Compare records before cleanup; see the duplicate cleanup article below. |
