Zisyl.
Talk to us
Migrations / ERPNext
ERPNext migration guide

Migrate from ERPNext

Use a dedicated ERPNext API user to analyze and move operational data into a tenant without copying authentication material.

Prerequisites

An ERPNext site reachable over HTTPS.
A dedicated ERPNext user with read access to the records being migrated.
An API key and API secret generated for that user.
Tenant admin access to Zisyl Migration Center.

Data coverage

Source records currently supported by the shared migration engine.

Zisyl areaSource recordsMigration behavior
Users / EmployeesUser, EmployeeInactive users with secure activation invitations; passwords and MFA are excluded.
CRMCustomer, Contact, OpportunityCustomers, contacts, and deals with duplicate matching.
ProjectsProject, TaskProjects migrate before their related tasks.
Support / KnowledgeIssue, Wiki PageTickets and company knowledge articles.
CalendarEventCompany events and scheduling details.
AccountingAccount, Supplier, Sales Invoice, Purchase InvoiceAccounts, vendors, invoice headers, balances, and bills.

1. Prepare ERPNext

Create a dedicated migration user so access can be reviewed and revoked independently.

  1. 1Create or select an ERPNext user for the migration.
  2. 2Grant read access only to the DocTypes you intend to move.
  3. 3Generate an API key and API secret for that user.
  4. 4Confirm the ERPNext site URL uses HTTPS and is accessible from your deployment.

2. Connect the source

Save the site URL and API credentials in the tenant Migration Center.

  1. 1Sign in as a company admin and open Admin → Migration Center.
  2. 2Choose ERPNext under Connection.
  3. 3Enter the site URL, API key, API secret, and per-data-type limit.
  4. 4Save and run Test. Secrets are encrypted and are never returned to the frontend.

3. Choose and map data

Select only the modules you need and review the default ERPNext field mappings.

  1. 1Open Plan & map and deselect unused data types.
  2. 2Expand Field mapping to change source field names when ERPNext is customized.
  3. 3Choose Update, Skip, or Create a separate copy for duplicates.
  4. 4Keep user invitations enabled if migrated users should activate accounts immediately.

4. Run the dry run

Validation reads ERPNext and builds a durable record-by-record migration plan.

  1. 1Run validation and wait for all selected DocTypes to be analyzed.
  2. 2Review create, update, skip, conflict, and invalid totals.
  3. 3Resolve duplicate rows individually when the default policy is not appropriate.
  4. 4Correct source permissions or field mappings and run another dry run when needed.

5. Migrate and verify

Start the approved plan and let background workers process it in dependency order.

  1. 1Start migration after the report is clean.
  2. 2Resume paused work or manually process the next batch if required.
  3. 3Verify representative projects, tasks, customers, tickets, and financial records.
  4. 4Use rollback if the imported result is not acceptable.

Do not rotate or revoke the ERPNext API key until the migration has completed.

Rollback restores updated records and removes records created by the run.

Authentication material never migrates

Passwords, password hashes, MFA secrets, sessions, API keys, and OAuth tokens are excluded. Users are matched by email and invited to establish fresh credentials.

Ready to validate your source?

Sign in as a tenant admin and open Admin → Migration Center.

Open Zisyl