> For the complete documentation index, see [llms.txt](https://pair.guides.gov.sg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pair.guides.gov.sg/nhg-health-domain-harmonization.md).
# NHG Health Domain Harmonization
As part of NHG’s email domain harmonization, your Pair Chat accounts will be migrated from your existing domains (e.g. `@imh.com.sg`, `@nsc.com.sg`) to the new unified domain: `@nhghealth.com.sg`.
This will happen in waves by institutions, and you’ll receive a notification ahead of your cut-over date.
### 🆕 What’s Changed from the Previous Guide (As of Aug 15)
Previously, we shared that your data would be automatically migrated on your cut-over date and that you will not be able to login with your old email address.
**Now:**
* On your cut-over date, your existing chats and Assistants will still be migrated to your **new** @nhghealth.com.sg account.
* If you log in **with your new email address**, you’ll see your migrated data.
* If you log in **with your old email address**, you’ll see a blank account and a banner.
* **Important:** Any new data you create in your old account *after* your cut-over date will **not** be migrated.
You will lose access to your old account completely by **25 September**.
***
#### What will happen on my agency’s cut-over date?
* Your Pair Chat data (chats and Assistants) will be automatically migrated to your new `@nhghealth.com.sg` email address.
* From that day onwards, you must log in using your new email address to access your data.
* Logging in with your old email will show you a blank account.
***
**How do I know if I've been successfully migrated?**
You will receive an **email notification from the Pair team** once your data has been successfully migrated to your new @nhghealth.com.sg account.\
This email will confirm that:
* Your migration is complete
* You can now log in using your new email address to see your data
***
#### Will I lose any data?
No — as long as you switch to your new `@nhghealth.com.sg` email address immediately after your cut-over date.\
\
If you continue using your old account after the cut-over date:
* Any new chats or Assistants you create there will **not** be migrated.
* You will lose access to the old account (and anything on it) after **25 September**.
***
#### I'm an Assistant creator! Do I need to do anything?
If you've created Assistants that were shared only with your old domain (e.g. `@imh.com.sg` or `@nsc.com.sg`), those Assistants will now be shared with users on `@nhghealth.com.sg`.
If you do not want your Assistant to be discoverable to others in the new domain, you can change its visibility from **"Discoverable"** to **"Link only"**.
[View guide to changing sharing settings](https://wise.pair.gov.sg/features/custom-assistants/first-asst#sharing-settings)
***
#### When is my cut-over date?
There are multiple waves for different NHG institutions. If you're not sure when your account is scheduled for migration, please check with your institution's IT team.
***
#### Need help?
If you have questions or run into issues after the migration, please contact the Pair team at\
****
***
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://pair.guides.gov.sg/nhg-health-domain-harmonization.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.