Country Mapping Behavior

This section outlines how legacy country entries from Version 1 are mapped to their updated counterparts in Version 2, which follows the ISO 3166-1 standard.

The mapping ensures backward compatibility while aligning all current and future data with standardized country codes and names:

Legacy Entry (version 1)	Latest Version (ISO 3166-1) (version 2)	Mapping Behavior
Swaziland	Eswatini	Automatic Replacement For countries with updated names (e.g., Swaziland → Eswatini). The system will automatically map and display the updated name (e.g., Eswatini) in the UI, including on the Detail Page, Listing Page, and other relevant areas.
Netherlands Antilles	Bonaire, Sint Eustatius and Saba Curaçao Sint Maarten (Dutch part)	Legacy Display with Guidance The original name will still be shown for legacy country names without a direct one-to-one mapping, such as the Netherlands Antilles. However, we recommend mapping to the corresponding updated countries where possible.
N/A	South Sudan	Newly added in Version 2

---

Impact on Data Import and Display

Use Case	Example	Behavior
Data with one-to-one mapping	Swaziland → Eswatini	During Import (File Upload / API) If a legacy country name like Swaziland is used, the system will accept it and automatically map it to the updated name, Eswatini. How it's displayed? Record will then show the latest country name in the system. (e.g., Eswatini)
No Direct Mapping (One-to-Many)	Netherlands Antilles → Bonaire, Sint Eustatius and Saba Curaçao Sint Maarten (Dutch part)	During Import (File Upload / API) If a legacy country name like theNetherlands Antilles is used, the system will accept it and will save it as it is. How it's displayed? Record will still show the legacy country name in the system. (e.g., Netherlands Antilles) Action Required To comply with the ISO 3166-1 standard, it is recommended that you map the legacy name to the latest version.