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

ERPNext Version 16 / Develop

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 upgrade Navari CSF Kenya before Kenya Compliance via Slade360 Advantage.

The compliance application contains data migrations that depend on structures introduced by newer versions of Navari CSF Kenya. Upgrading both applications together, or upgrading Kenya Compliance via Slade360 Advantage first, may result in:

• Failed migrations
• Incomplete data transfers
• Missing compliance mappings
• Migration errors
• Potential data loss

The recommended upgrade sequence is:

1. Upgrade Navari CSF Kenya
2. Run migrations
3. Verify successful migration
4. Upgrade Kenya Compliance via Slade 360 Advantage
5. Run migrations again
6. Verify compliance functionality
7. Remove legacy fields if required

Step 1: Upgrade Navari CSF Kenya

Update the application:

bench update --apps csf_ke

Run migrations:

bench --site <your-site> migrate

Wait for the migration to complete successfully before proceeding.

Step 2: Upgrade Kenya Compliance via Slade 360 Advantage

Once Navari CSF Kenya has been upgraded successfully, update the compliance application:

bench update --apps kenya_compliance_via_slade

Run migrations again:

bench --site <your-site> migrate

Allow all migration patches to complete successfully.

Step 3: Verify the Upgrade

After both applications have been upgraded:

• 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

Successful completion of these checks indicates that the migration completed correctly.

Legacy Field Cleanup

Some older versions may leave behind obsolete custom fields after migration.

Once you have confirmed that:

• All migrations completed successfully
• Existing compliance data is available
• Transaction submissions are functioning correctly
• eTIMS Ledger records are accessible

You may use the cleanup options available in the settings area to remove legacy custom fields.

⚠️ Do not remove legacy fields before confirming successful migration, as they may be required during troubleshooting or data verification.

Frappe Cloud Upgrades

For Frappe Cloud installations, follow the same upgrade order:

1. Update Navari CSF Kenya
2. Allow migrations to complete
3. Verify successful migration
4. Update Kenya Compliance via Slade360 Advantage
5. Allow migrations to complete
6. Verify compliance functionality

The same sequencing rules apply to prevent migration failures and ensure that all compliance data is preserved.

Need Assistance?

Slade 360 Advantage Onboarding

etims@savannahinformatics.com

Technical Support

support@navari.co.ke