> For the complete documentation index, see [llms.txt](https://docs.phocassoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.phocassoftware.com/budgets-and-forecasts/owner-and-administrator/import-a-budget-or-forecast.md). # Import a budget or forecast Import a budget or forecast file to use as the stream in the baseline data structure of a budget or forecast workbook. {% hint style="info" %} User permissions: Budgets & Forecasts and Manage Budgets & Forecasts {% endhint %} While it's not possible to import a budget *directly* into Budgets and Forecasts, you can import the budget file as a stream in a Phocas database. Then in Budgets & Forecasts, you can create a new budget based on that database, selecting the imported budget stream as the baseline data structure.
The import process is done in Designer and requires administration user permissions. See the following pages for detailed steps: * [Add a budget file to a non-financial database (easy budget upload)](/administration/designer/add-budget-file-to-non-financial-database.md) * [Add a budget file to a financial database](/administration/designer/add-a-budget-file-to-a-financial-database.md) --- # 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.phocassoftware.com/budgets-and-forecasts/owner-and-administrator/import-a-budget-or-forecast.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.