Live in under two working days, once your data is ready.
That caveat matters, so we put it in the headline. The software configures quickly. Assembling accurate data from your current tools is the part that takes real effort, and it is the part we help with most.
Scoping call
We map how you operate today: services, resources, package templates, commission rules, and which branches go first. If your setup does not fit Nolira, this is where we say so.
Output: A written scope and a go-live date
Data templates
We send templates for staff, services and prices, customers, and outstanding package balances. This is almost always the slowest part, because the data lives in several places. We help you clean it.
Output: Completed templates from your team
Staging import
Everything is imported into a staging environment first, never straight into production. Nothing you do here can damage live data.
Output: A working copy of your business to inspect
Validation report
We produce a report of duplicates, missing fields, conflicting prices and package balances that do not reconcile. You review a sample and sign off before anything goes further.
Output: Your written sign-off on a sample
Configuration
Roles, approval limits, discount thresholds, commission rules, resources, business hours and tax settings. Commission rules are tested against real past transactions so the numbers match what you already paid.
Output: A configured branch that reproduces your last month
Training
Separate sessions by role. Reception and cashier get the longest, because they carry the workflow. Managers cover approvals and closing. Owners get the reporting view.
Output: Staff who can work without supervision
Cutover and go-live
A final delta import brings across anything that changed while you were preparing. Opening package liability and stock counts are confirmed with you, then the branch goes live.
Output: Live operations with confirmed opening balances
Hypercare
Faster response while the team builds habits. Most questions arrive in the first three days, and most of them are about checkout edge cases rather than the system itself.
Output: A branch running without needing us
What to have ready
You do not need it perfect. You need it complete enough that the validation report is short. Send us whatever you have early and we will tell you what is missing.
- Your staff list with roles and which services each person performs
- Your service list with duration, price and any branch-specific pricing
- Your customer list with phone numbers, ideally deduplicated
- Outstanding package and membership balances per customer
- Your current commission rules, however they are written down
- A stock count for products you want tracked from day one
What usually slows a migration down
None of these are software problems, which is exactly why they catch businesses out.
Package balances that do not reconcile
This is the most common blocker. If two records disagree about how many sessions a client has left, someone has to decide which is correct before go-live. We surface every one of them rather than picking silently.
Duplicate customer records
The same client entered three times across three branches. We flag likely duplicates for a person to merge, because automatic merging of client history is not something to guess at.
Commission rules nobody wrote down
Often the rule lives in one person's head with exceptions accumulated over years. Expect to spend real time here. It is also usually where the first savings appear.
Send us a sample of your data.
One month of bookings and your package balances is enough for us to tell you how clean the migration will be, before you commit to anything.