Migrating from SmartShell to IZI: Step-by-Step Guide
Migrating from SmartShell to IZI: Step-by-Step Guide
Section titled “Migrating from SmartShell to IZI: Step-by-Step Guide”Moving from SmartShell isn’t just a tool swap — it’s a shift to a unified operational platform. After the migration, the club has PC management, POS, client database, bar, warehouse and analytics in one interface instead of a stack of separate systems.
What Changes
Section titled “What Changes”| Before (SmartShell + separate tools) | After (IZI) |
|---|---|
| SmartShell — PC management | IZI Hall — PC and session management |
| Separate POS system | IZI POS — built into the platform |
| Spreadsheets or separate CRM | IZI Clients — unified database |
| No bonus automation | IZI Automation — no-code rules |
| No business analytics | IZI Analytics — revenue, ARPU, load |
Step 1. Inventory Your Current Setup
Section titled “Step 1. Inventory Your Current Setup”Before starting, document:
- Number of hall PCs and their configuration
- Active tariffs (day/night/weekend/zone-based)
- Whether you have a client database and in what format
- Other software in use (POS, bar, accounting)
Step 2. Configure IZI Before Switchover
Section titled “Step 2. Configure IZI Before Switchover”Set up IZI in parallel while SmartShell is still running:
- Organization and venues
- Tariffs: day, night, zone-based, multi-pass
- Client groups and automation rules
- Bar menu and stock items (if applicable)
Step 3. Migrate Client Database
Section titled “Step 3. Migrate Client Database”If you have a client database in SmartShell or a separate CRM:
- Export to CSV (phone, name, balance)
- Check for duplicates
- Import into IZI via the built-in import tool
If there’s no client database, skip this step.
Step 4. Install the IZI Client on Hall PCs
Section titled “Step 4. Install the IZI Client on Hall PCs”The IZI installer deploys the IZI client (IZI agent) on each hall PC. The agent handles session management, PC monitoring, and communication with IZI CRM. Note: IZI Boot is a separate paid server-side product — it stores the master disk image on the IZI Boot server and handles disk protection and network-based PC reset. Process for installing the client:
- Download the IZI client installer from the admin panel
- Install on each PC (or deploy via network)
- Confirm each PC appears in the Hall section of IZI CRM
Step 5. Switchover Day
Section titled “Step 5. Switchover Day”Choose a low-traffic period. On that day:
- Deactivate SmartShell on PCs (or deactivate licences)
- Verify all PCs are active in IZI
- Run a few end-to-end test sessions
- Switch POS to IZI
- Open the first shift in IZI
Step 6. Train the Team
Section titled “Step 6. Train the Team”Workflows to practice:
- Starting and stopping a session
- Accepting payment and topping up balance
- Taking a bar order
- Opening and closing a shift
- Looking up a client and applying a bonus manually
IZI provides onboarding materials and support.
What Stays the Same
Section titled “What Stays the Same”- Player experience: same PCs, same games
- Tariffs carry over with the same prices (just reconfigured in IZI)
- No data loss with a correct migration
See also: IZI vs SmartShell comparison · Why choose IZI
Frequently asked questions
SmartShell protects PCs — does IZI do that too?
Yes. IZI Boot creates a master disk image and allows any hall PC to be restored in minutes. This covers the core OS protection use cases.
How long does migration from SmartShell take?
Usually 3–7 business days. Most of the time goes to tariff configuration and staff training, not the technical data transfer.
Do we need to reinstall software on each PC?
The IZI client (IZI agent) is installed on each hall PC via the IZI installer. The process takes a few hours and is usually done during off-hours or planned maintenance.
We use SmartShell with a separate POS — how does that change?
IZI includes POS as part of the platform. After migration, the separate POS is no longer needed — your operational stack simplifies significantly.