> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/health/v1.5/introducing-health/release-notes/hcm-v1.4-release-notes/migration-from-v1.3-to-v1.4.md).

# Migration from v1.3 to v1.4

The HCM v1.4 release requires migration of the boundary and MDMS data if the server is not a fresh deployment but an existing v1.3 deployment

### Boundary v2 migration

If the current environment has boundary data in MDMS v1 please follow the steps mention in the document below to migrate to boundary v2.\
\
[Boundary migration from v1 to v2 LTS](https://core.digit.org/platform/core-services/boundary-service/migrate-old-boundary-data-steps) 

### MDMS v2 migration

If the environment is new the one click installer and data loader will by default load the data required. 

If the Environment has pre existing data then the MDMS v2 migration tool should be run using the below document:

[MDMS migration from v1 to V2 LTS](https://core.digit.org/platform/core-services/mdms-v2-master-data-management-service/mdms-migration)

Following is the code link:

[Code link for the above-mentioned migration utilities](https://github.com/egovernments/Digit-Core/tree/core-2.9-lts-mvn-check/utilities)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.digit.org/health/v1.5/introducing-health/release-notes/hcm-v1.4-release-notes/migration-from-v1.3-to-v1.4.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.