Switching
Moving is the part everyone dreads. Here is exactly what it involves.
Whether you run another ERP, spreadsheets, or paper registers — the honest answer to “how painful is switching?” is below, step by step.
Students bulk-import into the right classes from a spreadsheet. Staff import from CSV with password-set invites. The library loads from a spreadsheet or MARC file — up to 500 rows a go, with a per-row rejection report so nothing silently disappears.
Loan matrices, fee books, approval chains, roles and gate screens are configured to how the institution already works. The demo you saw was already running on your rules — go-live is the same configuration, kept.
Nothing forces a big bang. Most schools start with the gate or the library — a module the old system never had — while attendance and fees keep running wherever they run today. Modules switch on per campus, and the server refuses what isn't enabled.
The first-admin onboarding wizard and the per-campus setup checklist show exactly what's configured and what isn't. Your dedicated team — the same people on the price ledger — do the loading with you.
Registers and reports export to CSV throughout. If Giiki ever stops earning its place, your data leaves with you. We'd rather keep you by being good than by being sticky.
What we won’t promise: a date for anything dependent on hardware you haven’t bought yet, or a “zero-effort migration”. Loading a school takes real work — that’s why the engagement includes a dedicated team instead of a support ticket queue.