Data migration and onboarding
Move into HisabERP without losing control of the source.
A successful migration is not simply an imported file. It is a documented transition in which master data, opening balances, users and daily workflows are prepared, tested, reconciled and approved.
Source preservedDry run requiredBusiness approvalControlled cutover
b.Biloo ERP
Data onboarding workspace
Migration control
| Reference | Date | Record | Branch | Amount | Status |
|---|---|---|---|---|---|
| INV-26-0891 | 31 Aug 2026 | Customers & suppliersMaster data | Addis HQ | ETB 126,500 | Paid |
| INV-26-0890 | 30 Aug 2026 | Opening stockControl total | Adama | ETB 89,760 | Approved |
| INV-26-0889 | 29 Aug 2026 | Cutover approvalGo-live gate | Hawassa | ETB 45,600 | Partial |
| INV-26-0888 | 28 Aug 2026 | Customers & suppliersMaster data | Addis HQ | ETB 73,200 | Posted |
| INV-26-0887 | 27 Aug 2026 | Opening stockControl total | Mekelle | ETB 18,975 | Review |
Where businesses start
A migration path for the records you already use.
The correct approach depends on the quality, ownership and operational importance of the source—not only its file format.
Excel and CSV files
Clean and map customers, suppliers, products, prices and approved opening balances into structured import files.
Notebooks and paper ledgers
Choose a practical cutover date and capture active master data and opening positions instead of retyping every historical page.
Other business software
Export source records, identify the system of record for each data type and preserve specialist tools that still have a valid role.
Multiple branch files
Standardize names, codes, units and branch ownership before consolidating separate operating records.
Controlled implementation path
Six stages from assessment to stable operations.
Every stage produces evidence for the next decision. A technical import is not treated as complete until the business reconciles and approves it.
Assess
Document the current systems, data owners, record volumes, required history, branch structure and highest-risk workflows.
Prepare
Clean duplicates, standardize identifiers, map fields and freeze approved source files for the dry run.
Configure
Set up the organization, users, roles, products, locations, fiscal context and required modules before loading live data.
Dry run
Import into a controlled workspace, inspect errors and compare record counts, quantities and financial control totals.
Validate
Require named reviewers for sales, inventory and finance to approve the migrated position and operating workflow.
Go live
Freeze the source, load approved opening positions, monitor the first operating period and keep old records read-only for evidence.
Preparation templates
Start with consistent column names and one record per row.
These CSV templates are preparation aids. Final import support and required fields depend on the agreed implementation scope and current product workflow.
Read the complete import preparation guide →Shared responsibility
Clear ownership prevents hidden migration risk.
HisabTech can support configuration and data movement, but the business remains responsible for source accuracy and approval.
Your business
- Name a migration owner and data reviewers
- Provide complete source exports and supporting statements
- Resolve duplicates and approve opening balances
- Control the source freeze and staff readiness
- Retain historical evidence after cutover
HisabTech
- Provide preparation templates and field guidance
- Configure the agreed HisabERP workspace scope
- Run or support controlled import dry runs
- Report validation exceptions clearly
- Support training and the agreed go-live window
Choose the right level of assistance
Migration services are scoped separately from the software subscription.
The assessment determines record volume, source complexity, required history, number of branches and validation effort before a final quotation is issued.
Self-guided preparation
Use the public templates and help guides to prepare data, then create the organization and validate records internally.
- CSV preparation templates
- Public migration checklist
- Help-center guides
- Standard product onboarding
Assisted migration
HisabTech reviews scope, supports mapping and dry-run validation, and coordinates a documented cutover with business reviewers.
- Migration assessment
- Field mapping review
- Dry-run exception report
- Opening-balance validation session
Complex implementation
A separately quoted project for large volumes, several source systems, complex branches or integration dependencies.
- Phased migration plan
- Source-system mapping
- Branch-by-branch validation
- Custom implementation scope
Important migration principle
Compare HisabERP with ExcelDo not migrate bad data faster.
Duplicates, unsupported balances and unclear ownership should be resolved before cutover. Old source records should remain preserved until the organization confirms the new workspace is stable and required evidence is retained.
Plan the transition before importing
Start with a migration assessment based on your real source data.
Share the source systems, approximate record volumes, branch structure and target go-live period. HisabTech will identify the preparation and validation path.