> For the complete documentation index, see [llms.txt](https://docs.navigaglobal.com/newsroom-planner/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.navigaglobal.com/newsroom-planner/6.3.0/admin-guide/migration/3.x-4.x.md).

# 3.x ➡ 4.x

## The steps you need to do

1. Fulfil the requirements (for example Content Agent 2.0 is required)
2. Make sure you have a correct Writer version according to the requirements, and fulfil any other requirements
3. Save your templates as XML files from you current NRP settings - if you have made changes to your templates
4. Update necessary Open Content Configuration to the latest versions – setup a task for DevOps
   1. Writer Article Template Configuration Yaml (to get TemplateIsShared configuration)
   2. Naviga Units Yaml
   3. NRP Config Yaml
   4. NRP Templates Config Yaml
   5. Create OC import group rules for templates
5. Create and save the templates on file (for all your content types), according to the Template page. 
6. Create new templates to Open Content using the Template Handler application. 
7. Add assignments uuid property to fetch in Plugin settings if it's missing (this is done automatically when resetting configuration):
   1. Go to Plugin settings -> Configurations (see image below)
   2. Open the "Property fetching" section, and navigate to "SingleView"
   3. Add the line: `"planningItem.assignments.uuid"` if it doesn't already exist
   4. Save your new config
8. Upgrade Newsroom Planner plugin. 

![](https://content.gitbook.com/content/uwSMGZPahvqvTGdlbIzV/blobs/4UhYWnZZwtHd3sINEDkQ/image.png)

## Templates config

{% content-ref url="/pages/-MLDKeBszxrA855VOL4g" %}
[Templates](/newsroom-planner/6.3.0/admin-guide/migration/3.x-4.x/templates.md)
{% endcontent-ref %}


---

# 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://docs.navigaglobal.com/newsroom-planner/6.3.0/admin-guide/migration/3.x-4.x.md?ask=<question>&goal=<endgoal>
```

`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.