Skip to main content

Export and import a portfolio

A portfolio can move from one HocNota environment to another — from staging to production, from one organization to another — in a .hnp file (HocNota portfolio).

What the file contains​

The file holds everything needed to recreate the portfolio, without any data:

ContentCarried over
The portfolioFull graph (nodes, links, notes), description, duration limit, annotations JSON output
The agentsFull definition: role, objective, constraints, prompt, extraction passes
The knowledge basesSettings only: type, chunking, embedding model, RAG options, RAG profile. No documents, no index
AI, embedding, OCR and decision models, RAG profilesTheir name, to find their counterpart on import
Skills, MCP connectors, HNS packagesTheir name only (a connector never carries its secrets)

Not carried over: knowledge base documents and indexes, jobs and their history, agent memory, data produced by HNS nodes, the teams and API keys that have access to the portfolio.

The file is a readable JSON document.

Export​

Two entry points:

  • in the Designer, a portfolio's ⋯ menu → Export (.hnp);
  • in the editor, the ⤓ button of the top bar. The export uses the saved version: save your pending changes first.

You must be allowed to read the portfolio's agents and knowledge bases: the file holds their definition.

Portfolio that runs other ones​

A portfolio holding a Pipeline node does not embed the portfolio it runs: each sub-portfolio has its own .hnp file. The export then opens a window listing every file — the exported portfolio, then each sub-portfolio, even indirect ones. Download them one by one or with Download all.

Import​

In the Designer, open the destination folder, click Import a portfolio and choose the .hnp file. HocNota analyzes the file and shows you, before creating anything, what it is going to do.

Portfolios used​

For each sub-portfolio:

  • Provide its .hnp file… — the sub-portfolio is imported along with the portfolio (and its own sub-portfolios are asked for in turn);
  • or map it to an existing portfolio of this environment;
  • or leave it empty: the Pipeline node will have to be set up again.

Agents​

For each agent of the file, choose:

  • Create from the file — a new agent is created with the exported definition;
  • or an existing agent, used instead in the portfolio.

An existing agent with the same name is suggested by default. Creating one requires the right to write agents.

Knowledge bases​

Same choice: create the knowledge base (settings only, no documents) or use an existing one. A created knowledge base is empty: add its documents, then run the indexing.

Without the Advanced indexing option, a created knowledge base does not get its advanced settings (contextual retrieval, reranking, parent/child, OCR parsing engine): the imported portfolio's note says so.

Models and settings​

For each AI model, embedding model, OCR model, decision model, RAG profile or storage space referenced, HocNota suggests its counterpart from its name (then from the model name at the provider). You can pick another one, or None: the default setting then applies.

Not found in this environment​

Skills, MCP connectors and HNS packages are not imported from a portfolio. If they exist here under the same name, they are reused; otherwise the node involved is left empty.

After the import​

The imported portfolio:

  • is created inactive, in the folder shown, along with the created agents and knowledge bases;
  • is exposed neither to the API nor as an MCP server — turn these back on in ⚙ if needed;
  • opens straight in the editor.

When something could not be carried over, an orange note is placed at the top of the graph listing what is left to do: skill, MCP connector or HNS package to install, sub-portfolio not imported, model without counterpart, knowledge base to fill, writers and external file of an HNS node to set again. Once the portfolio is complete, delete the note.

If a name is already taken, the imported item gets the « (import) » suffix.