Migrating from Langame to IZI: Step-by-Step Guide
Migrating from Langame to IZI: Step-by-Step Guide
Section titled “Migrating from Langame to IZI: Step-by-Step Guide”Moving from Langame to IZI is a planned operation that can be done with minimal downtime. The main task: transfer the client base with balances, recreate the tariff structure, and switch the first shift to IZI so that clients don’t notice any disruption to hall operations.
This guide covers the migration methodology: what to prepare, the correct order of steps, what data transfers and what doesn’t, and what to do if problems arise.
Note: the availability of an automatic import tool from Langame and supported file formats — check with the IZI team before starting. Some steps may be automated depending on your Langame version.
What transfers, what doesn’t
Section titled “What transfers, what doesn’t”A clear understanding of the migration boundary matters more than anything else. If you promise a client “everything will be saved,” you need to know exactly what that means.
Transfers
Section titled “Transfers”| Data | Migration method |
|---|---|
| Client database (names, phones, emails) | CSV import or manual entry |
| Current balance per client | Top-up in IZI when creating the client |
| Tariff structure (hourly, night, subscriptions) | Manual recreation in IZI CRM |
| Zone categories | Recreation in IZI (new zone structure) |
Does not transfer
Section titled “Does not transfer”| Data | Why |
|---|---|
| Transaction history | Different storage formats; history stays in Langame |
| Session history | Same reason |
| Client gaming statistics | Langame-specific format |
| Screensaver and display settings | Resources are recreated in IZI |
Langame history is not deleted when you leave — keep access for at least a month after migration to verify disputed situations.
Preparation: what to do in Langame first
Section titled “Preparation: what to do in Langame first”Step 1. Export the client database
Section titled “Step 1. Export the client database”In the Langame CRM, export the client list with the following fields:
- Name / username
- Phone (primary identifier in IZI)
- Email (if available)
- Current gaming balance
Export format: CSV or Excel. Save the file and verify that the balance is current as of the export date.
Step 2. Record the tariff structure
Section titled “Step 2. Record the tariff structure”Create a table of all active tariffs:
- Tariff name
- Type (hourly, night, subscription for N hours)
- Price
- Zone (if zone-based)
- Currently active?
This is your reference when recreating tariffs in IZI.
Step 3. Check clients with subscriptions
Section titled “Step 3. Check clients with subscriptions”Clients with remaining hours on a subscription are the priority. Create a list: client → remaining hours → monetary equivalent at the hourly rate. You’ll decide how to transfer these balances in the next step.
Step 4. Choose a switch date
Section titled “Step 4. Choose a switch date”The ideal switch point is the start of a new shift during off-hours (early morning, after closing). The Langame shift closes, the first IZI shift opens.
Setting up IZI in parallel with Langame
Section titled “Setting up IZI in parallel with Langame”Running both systems in parallel is the standard and safe approach. Langame continues to run real shifts while IZI is configured and tested.
Step 5. Create the organization and club in IZI
Section titled “Step 5. Create the organization and club in IZI”If you don’t have an IZI account yet — owner registration and create an organization.
Step 6. Set up zones in IZI
Section titled “Step 6. Set up zones in IZI”Recreate the zone structure from Step 2. Zone names in IZI can match Langame — it’ll be more familiar for administrators.
Step 7. Connect devices
Section titled “Step 7. Connect devices”Install the IZI client on each computer in the hall using the IZI client installer. Link machines to the club via UUID. Assign each device to the correct zone.
Details: Quick start in 15 minutes — blocks 1 and 2.
Step 8. Recreate tariffs in IZI
Section titled “Step 8. Recreate tariffs in IZI”Using the table from Step 2, create tariffs in IZI:
- Hourly → Type “Hourly,” price, zone
- Night → Same type + schedule (reduced-rate hours)
- Subscriptions → Type “Multipass,” hour package, package price
→ How to create your first tariff
Step 9. Add staff
Section titled “Step 9. Add staff”Invite administrators, assign roles. In IZI, roles are configured via Organization → Roles.
→ Inviting staff, Owner and administrator: permission differences
Step 10. Run a test shift in IZI without switching
Section titled “Step 10. Run a test shift in IZI without switching”Open a shift in IZI, run a test session, verify the tariff works, balances calculate correctly, and the shift closes properly. Langame continues running real shifts during this time.
Importing the client database
Section titled “Importing the client database”Step 11. Import clients
Section titled “Step 11. Import clients”Upload the CSV from Step 1 into IZI. Import section: Clients → Import.
Map CSV fields to IZI fields:
- Phone → “Phone” field (primary identifier; clients use this to link the mobile app)
- Name → “Name” field
- Email → “Email” field
If there’s no automatic import: create clients manually or contact IZI support — the team can help with non-standard Langame export formats.
Step 12. Transfer balances
Section titled “Step 12. Transfer balances”After creating clients, top up the balance for everyone who had a balance in Langame.
If there are many clients, ask the IZI team about bulk top-up via import with an “Initial balance” field.
Step 13. Decide what to do with subscriptions
Section titled “Step 13. Decide what to do with subscriptions”For clients with remaining subscription hours, there are three options:
Option A. Convert remaining hours to a monetary balance at the hourly rate and credit as a regular balance. Simple; the client sees no difference in the interface.
Option B. Recreate the subscription in IZI and assign it to the client manually via an administrator. Preserves structure but is more labor-intensive.
Option C. Inform clients that balances will be converted at a set rate — announce this in advance.
The switch: last shift in Langame → first shift in IZI
Section titled “The switch: last shift in Langame → first shift in IZI”Step 14. Notify clients about the switch
Section titled “Step 14. Notify clients about the switch”3–5 days before the switch:
- Announcement at the front desk / on hall screens
- Message to your group (if you have a social media or messenger group)
- Text: “Starting [date], the club runs on the new IZI management system. Your balances are saved. To access the mobile app, download IZI and log in with your phone number.”
Step 15. Close the last shift in Langame
Section titled “Step 15. Close the last shift in Langame”Standard Langame shift closing procedure. Ensure all active sessions are ended, the register is closed, and there are no discrepancies.
Step 16. Verify balances
Section titled “Step 16. Verify balances”Check balances for a few clients from your table against what’s in IZI. A random sample of 5–10 clients is sufficient.
Step 17. Open the first shift in IZI
Section titled “Step 17. Open the first shift in IZI”On the first day, stay nearby or stay in easy contact with the administrator. Typical first-shift questions: “where do I find a client,” “how do I move someone to another PC,” “where is the refund button.”
Common issues and how to handle them
Section titled “Common issues and how to handle them”Client not found in search
Section titled “Client not found in search”Possible causes:
- Phone number entered in a different format (+1 / without code / local format) — standardize format during import
- Client wasn’t in Langame’s database (guest sessions without a profile)
- Typo during import
Solution: find manually or create a new client, transfer balance via administrator.
Client balance discrepancy
Section titled “Client balance discrepancy”Possible causes:
- Client had a session in Langame between the export date and the import date
- Error in the “balance” column during import
Solution: compare with Langame session history for the export → switch period, adjust manually.
Device visible in CRM but not accepting sessions
Section titled “Device visible in CRM but not accepting sessions”Possible causes:
- IZI client not running on the device
- Shift not opened
- Tariff not linked to the device’s zone
→ Device not accepting sessions: diagnostics
CSV encoding issues during import
Section titled “CSV encoding issues during import”If client names appear garbled in CSV — ensure the file is saved as UTF-8. In Excel: Save As → CSV UTF-8 (comma delimited).
Rollback: what to do if something goes wrong
Section titled “Rollback: what to do if something goes wrong”Parallel IZI setup is specifically designed for a safe rollback:
- Langame is not shut down until the first 2–3 IZI shifts have run without issues
- If the first IZI shift has a critical failure — close the shift, return to Langame, diagnose the issue
- After fixing, attempt the switch again at the next convenient time
IZI data is not affected by rollback — it remains, and a shift can be reopened after the fix.
Downtime estimate
Section titled “Downtime estimate”With proper preparation, the switch takes 5–15 minutes — the time between closing the last shift in Langame and opening the first shift in IZI.
If the switch is done during off-hours, there is no downtime for guests at all.
What slows down the switch:
- Large number of clients with subscriptions requiring manual processing
- Non-standard export format from your Langame version
- Equipment that needs manual reconfiguration
After migration: the first 30 days
Section titled “After migration: the first 30 days”- Keep access to Langame for verifying disputed balances
- Export a transaction archive from Langame (all history) and save locally
- Analytics in IZI start from the first session — allow 2–4 weeks for meaningful reports to accumulate
- After 2 weeks, check average order value and hall utilization — these are the baseline for the next round of improvements
Related
Section titled “Related”- Club launch checklist: 30 steps — full setup route
- Connecting your first PC: installing the IZI client — installing the agent on computers
- Owner and administrator: permission differences — roles in IZI
- IZI subscription: plans and payment — cost after trial
- IZI vs Langame: platform comparison — feature comparison
Frequently asked questions
How long does a full migration from Langame to IZI take?
With all import data ready: one to two days. Typical scenario: IZI is set up in parallel, one shift runs in both systems simultaneously, then you switch completely. A large club with hundreds of clients and complex tariffs — plan three to five days.
What transfers from Langame to IZI?
What transfers: client database (names, phones, emails), current balances, tariff structure (recreated manually or via import). Transaction history in Langame stays in Langame — it is not imported into IZI as live history.
Will client balances be lost during the switch?
No, if the migration is done correctly. Balances are exported from Langame and imported into IZI as a top-up for each client. Clients see their balance in the IZI mobile app after linking their phone number.
Does the club need to close during migration?
Not necessarily. The recommended approach is to set up IZI in parallel and switch between shifts: close the last shift in Langame, open the first shift in IZI. Downtime is a matter of minutes.
What to do about subscriptions and multipass tariffs from Langame?
Clients with remaining hours on a subscription are the most sensitive case. The balance must be recorded manually and either converted to a monetary equivalent in IZI, or recreated as multipass tariffs. The exact approach depends on your tariff policy.
Will Langame notify clients about the switch?
Langame does not notify clients when you move to another system. Notifying clients is your responsibility. It is recommended to post an announcement in the club and send a message to the database a few days before the switch.
Is there an automatic import tool from Langame?
Check with the IZI team for the format and availability of automatic import tools — capabilities may depend on your Langame version and export format. In general, import is done via CSV files with client data.
What to do with Langame data after the switch?
Keep access to Langame for at least one month after migration — for verifying disputed client situations. Export and save a transaction archive for the entire period of operation.