Sometimes the relationship with your ERPNext provider stops working. Support is slow, changes take weeks, or they've simply gone quiet. Moving to a new provider is very doable, but the organisations that struggle are the ones that only discover what they're missing after they've switched.
Here's what to check before you make the move.
1. Who Owns the Server?
Find out where your system is hosted and whose account it's on. If the server or cloud account belongs to your vendor, you'll need a full copy of your system before you leave. If it's in your name, make sure you have the login details.
2. Do You Have Full Administrator Access?
You should have an administrator login to your own system, not just user accounts. Ask for it early, while the relationship is still working.
3. Where Are the Backups?
Ask where backups are stored, how often they run, and when one was last tested. You'll want a complete, recent backup of both the database and all attached files before anything moves.
4. Can You Get the Encryption Key?
ERPNext stores certain saved passwords and integration credentials in encrypted form. The key needed to read them sits in your system's configuration, not in the database. Without it, those stored credentials can't be recovered after a move and will have to be re-entered. Make sure the key is handed over along with the backup.
5. What Was Customised, and Where Is the Code?
List every custom field, script, report, print format and custom app. If your vendor built custom apps, you need the source code, ideally with access to where it's kept. Without it, a new provider has to rebuild those features.
6. Which Integrations Are Running?
Payment gateways, mobile money, SMS, email and bank connections all rely on credentials and settings. List each one, who holds the account, and what will need reconnecting.
7. Who Controls Your Domain?
If your system runs on your own web address, check who manages the domain and its DNS settings. Moving the system means pointing the address to its new home.
8. What Does Your Contract Say?
Check the notice period, any exit fees, and whether the vendor is obliged to hand over data and code. A clear exit clause makes everything smoother.
How a Good Takeover Works
A professional takeover starts with a review of everything above, then a full backup, a trial move on a separate copy, and checks with your team before the live switch. It's also the ideal moment to upgrade to a current version.
We recently took over three live ERPNext systems from a previous vendor and upgraded them from version 13 to 15 in one project. See the project
Thinking of switching? Book a discovery call and we'll start with a free assessment of your current setup.