We are migrating an old GNU Health 3.6 (Tryton 5.0) deployment to newer versions (3.8 → 4.0 → 4.4 → 5.0) due to database inconsistencies and legacy issues.
During the migration from GNU Health 3.8 (Tryton 5) to GNU Health 4.0 (Tryton 6), we encounter a blocking issue:
The OHADA chart of accounts is present (accounts and hierarchy exist), but it is not usable
When trying to reconfigure accounting with these accounts, the company is not correctly taken into account, we get inconsistent behavior such as: tiers requis : “vrai” tiers requis : " faux”
Important detail:
The original system was deployed without a dedicated accounting module; the OHADA chart seems to have been loaded manually or via a legacy process.
Pleass, what is the proper and safe way to restore a functional OHADA accounting setup on Tryton 6+ without losing existing data, knowing this is a migration and we are currently on a test server?
Any guidance, best practices, or similar migration experiences would be highly appreciated.
SYSCOHADA chart template was introduced only in series 7.2 so I doubt your installation is based on this one as you said it is on series 5.0.
So I do not think you should try to “reconcile” the existing setup with this new module.
Now the existing chart may have some inconsistency that needs to be solved one by one.
I’m a beginner with Tryton configuration, and it’s not really easy to perform advanced troubleshooting at this point.
If possible, I would appreciate a guide that will allow me to better understand Tryton’s configuration (preferably accounting with OHADA chart) in order to effectively resolve this issue.
The chart of account modules provide just template to create real chart of account for a company.
So you can not attach an existing chart of account (maybe created manually) to a new template. You must keep managing the chart of account manually.
