> For the complete documentation index, see [llms.txt](https://documentation.astera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.astera.com/report-model/miscellaneous/importing-monarch-models.md).
# Importing Monarch Models
### Overview
If you are a former Monarch user, you can use your Monarch models within Astera . You can load and convert your old Monarch files by opening up your Monarch .xmods in Astera. These models will automatically be converted to a usable report model. With the built in converter, the Monarch model logic is converted to Report model logic.
### Difference between Monarch models and Report Models?
The main difference between Monarch models and Report models is the type of data region used. Monarch models are all appended data. In Astera, the models consist of data regions with a parent-child hierarchy or a tree structure. This better represents how the data is extracted.
### Best Practices
* When converting your Monarch models, always make sure to preview your model to make sure everything is being extracted correctly.
* If your Monarch model is using a PDF, you may need to adjust the *Scaling Factor*.
### Video
### Example
1. Open Astera and click the *Open* icon placed in the icon bar.
2. A window will appear where you will need to select your Monarch model. Select your .xmod file and click *Open*.
3. Once you do this, the .xmod file would be loaded on to the Astera designer and a Report Options panel will appear. This is where you will select the source file of your .xmod file.
4. Once you select your file, Astera will convert the extension from .xmod to .rmd.
Now you have a usable report model. You can adjust this model or proceed to export settings. This concludes importing Monarch Models in Astera.
---
# 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://documentation.astera.com/report-model/miscellaneous/importing-monarch-models.md?ask=&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.