Transition from legacy to ERPNext - Revision history

Wikiadmin at 01:18, 6 January 2026

2026-01-06T01:18:06Z

← Older revision		Revision as of 03:18, 6 January 2026
Line 7:		Line 7:
	* 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.		* 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]]		* [[Statistics of Legacy before Migrating to ERPNext]]


			'''Resources:'''

			* [https://discuss.frappe.io/c/erpnext/6 ERPNext forum]
			* [https://docs.frappe.io/erpnext/introduction Introduction] doc
			* [https://www.youtube.com/watch?v=ZH2unYQHxlE Let's Learn ERPNext, Episode 1, ft. Dharmesh] tutorial video

	= From JIP 400 Service Center to ERPNext CRM =		= From JIP 400 Service Center to ERPNext CRM =

Wikiadmin at 01:18, 17 November 2025

2025-11-17T01:18:24Z

← Older revision		Revision as of 03:18, 17 November 2025
Line 5:		Line 5:
	'''Remarks:'''		'''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.		* 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]]		* [[Statistics of Legacy before Migrating to ERPNext]]

Line 22:		Line 22:
	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”.		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, ~~and~~ fill in the correct name in ERPNext CRM.		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 ===		=== Email Address ===
Line 42:		Line 42:

	== Primary Contact of Company Customer ==		== 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.		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 legacy vTiger Leads to ERPNext =

Wikiadmin at 01:17, 3 November 2025

2025-11-03T01:17:50Z

← Older revision		Revision as of 03:17, 3 November 2025
Line 6:		Line 6:

	* 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.		* 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.
	* [[~~Statics~~ before ~~System Migration~~ to ERPNext~~\|Statics before System Migration~~]]		* [[Statistics of Legacy before Migrating to ERPNext]]

	= From JIP 400 Service Center to ERPNext CRM =		= From JIP 400 Service Center to ERPNext CRM =

Wikiadmin at 01:16, 3 November 2025

2025-11-03T01:16:21Z

← Older revision		Revision as of 03:16, 3 November 2025
Line 6:		Line 6:

	* 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.		* 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.
			* [[Statics before System Migration to ERPNext\|Statics before System Migration]]

	= From JIP 400 Service Center to ERPNext CRM =		= From JIP 400 Service Center to ERPNext CRM =

Wikiadmin: /* For legacy vTiger Leads to ERPNext */

2025-11-03T00:35:15Z

For legacy vTiger Leads to ERPNext

← Older revision		Revision as of 02:35, 3 November 2025
Line 44:		Line 44:

	= For legacy vTiger Leads to ERPNext =		= For legacy vTiger Leads to ERPNext =
	For country name, city name, Email address, and phone number, you may see similar dummy.		For country name, city name, Email address, and phone number, you may see similar dummy like those of company customer.

	=== Job Title ===		=== Job Title ===
Line 54:		Line 54:
	=== Territory ===		=== Territory ===
	<code>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 } }</code>		<code>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 } }</code>
	Remarks: For company customers of JIP400 Service Centre, “territory” is fully migrated.

			Remarks:

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

Wikiadmin: Created page with "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 durin..."

2025-11-03T00:25:48Z

Created page with "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 durin..."

New page

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.

= 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:

# Company
# 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, and 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.

=== 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 ===
<code>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 } }</code>
Remarks: For company customers of JIP400 Service Centre, “territory” is fully migrated.