What Happens If We Change the Module of an Existing ERPNext DocType (Example: Employee)?

1

Hi everyone,

I have a question regarding changing the module of an existing standard DocType in ERPNext.

For example, the Employee DocType currently belongs to the ERPNext Setup module.

What would happen if I change the module of this existing standard DocType to my custom app module?

Specifically:

  • Will it affect existing data or records?

  • Will future ERPNext updates override the change?

  • Could this create migration or patch issues?

  • Are there any risks related to permissions, fixtures, or dependencies?

  • Is this considered a safe practice, or is it better to override/extend instead of changing the module directly?

I’d like to understand the potential issues or side effects before making such a change.

Thanks in advance!

2

Changing the module of a standard DocType (e.g., Employee) in ERPNext is not recommended.

Existing data : Safe, database records are unaffected.
ERPNext updates : Will override your change on every bench update/bench migrate.
Migration/patch issues : Patches reference the original module path, causing potential conflicts.
Permissions/fixtures : Fixture conflicts are likely; permission names still work but groupings may shift.

Use Frappe’s built-in customization layer instead — Custom Fields, Client/Server Scripts, Customize Form, and custom Workspaces.