Upgrade & Migration
This guide applies only to existing installations running versions older than the minimum supported releases listed below.
If you are performing a new installation, follow the standard Installation Guide instead.
Recent releases introduced significant structural improvements, updated compliance mappings, and new data migration processes. To ensure that existing compliance data is migrated correctly, upgrades must be performed in a specific order.
Version Requirements
Use this guide if your installation is running versions older than the following:
ERPNext Version 15
| Application | Minimum Version |
|---|---|
| Navari CSF Kenya | v2.10.0 |
| Kenya Compliance via Slade 360 Advantage | v15.10.0 |
ERPNext Version 16 / Develop
| Application | Minimum Version |
|---|---|
| Navari CSF Kenya | v16.4.0 |
| Kenya Compliance via Slade 360 Advantage | v16.4.0 |
If your installation already meets or exceeds these versions, normal application updates can be performed using standard Bench or Frappe Cloud update procedures.
Important Upgrade Order
⚠️ Always update the required dependencies before running the CSF Kenya migration actions.
The upgrade process now consists of:
- Update the required applications and dependencies
- Run database migrations
- Open Navari KRA eTIMS Settings
- Open the CSF KE Migration button group
- Run Run Data Migration
- Run Clear Hanging Field
- Verify the migrated data and compliance functionality
- Remove legacy fields if required
Do not run Clear Hanging Field before Run Data Migration.
The actions must be executed in the order shown above because the data migration may depend on structures introduced by the updated applications.
Step 1: Update Dependencies and Applications
Before performing the data migration, update the required applications to their supported versions.
Navari CSF Kenya
Update the application:
bench update --apps csf_ke
Run the site migration:
bench --site <your-site> migrate
Wait for the migration to complete successfully.
Kenya Compliance via Slade 360 Advantage
After Navari CSF Kenya has been successfully updated and migrated, update the compliance application:
bench update --apps kenya_compliance_via_slade
Run the site migration again:
bench --site <your-site> migrate
Wait for all migration patches to complete successfully before continuing.
⚠️ Do not run the CSF KE Migration actions until both applications have been updated successfully.
Step 2: Open Navari KRA eTIMS Settings
After the application updates and database migrations have completed:
- Open Navari KRA eTIMS Settings
- Locate the CSF KE Migration button group
- Run the migration actions in the following order.
Step 3: Run Data Migration
From Navari KRA eTIMS Settings:
CSF KE Migration → Run Data Migration
This action migrates existing compliance data to the structures introduced by the newer versions of Navari CSF Kenya and Kenya Compliance via Slade 360 Advantage.
Allow the process to complete before continuing.
Do not run Clear Hanging Field while the data migration is still in progress.
Step 4: Clear Hanging Field
After Run Data Migration has completed successfully:
CSF KE Migration → Clear Hanging Field
This action cleans up the remaining hanging or obsolete field references created by older versions.
⚠️ Always run Run Data Migration before Clear Hanging Field.
Step 5: Verify the Upgrade
After both migration actions have completed:
- Open Navari KRA eTIMS Settings
- Verify Companies, Clusters, Branches, and Workstations
- Verify Item and Customer synchronization records
- Review recent Sales Invoices and Credit Notes
- Confirm that eTIMS Ledger entries are accessible
- Confirm that scheduled jobs are running normally
- Confirm that new transactions can be submitted successfully
Successful completion of these checks indicates that the upgrade and data migration completed correctly.
Legacy Field Cleanup
Some older installations may still contain obsolete custom fields after migration.
Once you have confirmed that:
- All application updates completed successfully
- Database migrations completed successfully
- Run Data Migration completed successfully
- Clear Hanging Field completed successfully
- Existing compliance data is available
- Transaction submissions are functioning correctly
- eTIMS Ledger records are accessible
you may use the available cleanup options in the settings area to remove remaining legacy custom fields.
⚠️ Do not remove legacy fields before completing and verifying the migration. They may still be required during troubleshooting or data verification.
Frappe Cloud Upgrades
For Frappe Cloud installations, follow the same overall sequence.
1. Update Dependencies and Applications
Update Navari CSF Kenya first and allow its migrations to complete.
Then update Kenya Compliance via Slade 360 Advantage and allow its migrations to complete.
2. Run CSF KE Migration Actions
After both applications have been updated:
- Open Navari KRA eTIMS Settings
- Open the CSF KE Migration button group
- Run Run Data Migration
- Wait for it to complete
- Run Clear Hanging Field
- Verify the migration and compliance functionality
⚠️ The migration actions must be executed in this order.
Need Assistance?
Slade 360 Advantage Onboarding
etims@savannahinformatics.com
Technical Support
support@navari.co.ke