Transition from legacy to ERPNext

Garbage in, Garbage out.

Decent office automation depends on the quality of data, just like AI model training needs quality data with appropriate labeling. A decent CRM / ERP system helps users to maintain the correctness and integrity of data, therefore supports decent workflow automation and high productivity with less stress.

Remarks:

• This page will be retired in March 2026 when staffs are familiar with ERPNext and most if not all dummy data generated during migration have been resolved by the sales/marketing team.
• Statistics of Legacy before Migrating to ERPNext

Resources:

• ERPNext forum
• Introduction doc
• Let's Learn ERPNext, Episode 1, ft. Dharmesh tutorial video

From JIP 400 Service Center to ERPNext CRM

ERPNext maintain data models matching real world data and operation, while the CRM of JIP 400 Service Center is the result of programmers at the level of fresh grade student with less than 3 months academic experience, let alone commercial experience.

Company Customer

Long story short, 99% of company data has been imported to ERPNext as , over 95% of them are fully imported:

1. Company
2. Optional primary contact

From time to time after the production deployment of ERPNext, you will see some records are missing some fields which are actually filled with dummy data.

Country Name

You may see some addresses are with country name “Iceland”. This is because ERPNext maintains a list of valid country names, and only those matched will be accepted, with the exception of “USA” which has been translated to “United States”.

If you see “Iceland”, you may lookup JIP400 Service Center and find out the country name which is considered invalid by ERPNext, or do some more researches, then fill in the correct name in ERPNext CRM.

Email Address

You may see “dummy251023184244.123@legacy.com”.

The offender record has Email address in invalid format.

City Name

You may see “Dummy”, since ErpNext demands a city in some situations.

Phone Number

You may see “66666666”.

Remarks:

• Since ERPNext won’t allow street address 2 if street address 1 is not defined, the migration process also normalizes the street address 1 and street address 2, and move the address 2 to address 1 in such scenario.
• Region in ttonline DB is mapped to Territory.
• While in address, you have country “United States” predefined by ERPNext, and in Territory, you have “USA”.

Primary Contact of Company Customer

In ERPNext, a company customer must have a primary contact. If in JIP400 Service Centre, a company customer has no contact associated, the migration process creates a dummy primary contact like “LegacyJip400 Legacy accountName”, with not so dummy phone number and Email address.

For legacy vTiger Leads to ERPNext

For country name, city name, Email address, and phone number, you may see similar dummy like those of company customer.

Job Title

Mostly migrated from Designation. If designation is SalesMan, this is translated to null.

Lead Source

Mostly migrated, with “--None--” translated to null.

Territory

static string CountryToTerritory(string s) { switch (s) { case "Australia": return "AUSTRALIA"; case "USA": return "USA"; case "United States": return "USA"; default: return "ROW"; //null will result in Australia by default } }

Remarks:

• For company customers of JIP400 Service Centre, “territory” is fully migrated.