Import guides
OneNote
What to hand Canonry
Use File > Export in the OneNote desktop app: pick Section and save it as OneNote Section (.one), or pick Notebook and save it as OneNote Package (.onepkg). Hand Canonry the file, on its own or zipped. This is the format OneNote itself reads back, and it is the only export that records where each page sits in your notebook, so a subpage is proposed as a subpage rather than as one more page.
Failing that, export one section at a time as Single File Web Page (.mht) from the desktop app, and hand Canonry each file, on its own or zipped. It is OneNote's own export, it needs no other tool, and every page in it becomes its own entry rather than one long document. What it does not carry is the hierarchy.
A folder tree of individually exported pages, one file per page, carries the same hierarchy .one and .onepkg do and is read the same way. It exists because it used to be the only way to get that, and OneNote has no menu item for it: producing it means running a script against the GetHierarchy and Publish automation calls the desktop app exposes, for example meichthys/onenote-html-export, a free, open-source tool built for exactly this. Zip the folder it produces and upload that, since the upload box takes one file rather than a folder. If File > Export is available to you, it is less work for the same result.
Failing all of those, print one section at a time to PDF, or export it to DOCX, and hand Canonry that. It is read through the PDF or DOCX guide, the same as any other PDF or DOCX, and it loses the notebook's own structure: every page becomes one long document and a subpage becomes just another heading. Whole-notebook scope drops pages here as well. Canonry can tell that a PDF came out of OneNote’s own printer, and it can tell from the page footers when a print covers more than one section, so it says both on the confirmation screen rather than letting you think everything came across.
One thing the export menu offers is refused, and refused before an import starts rather than partway through it, so nothing is spent on it: XPS (.xps). It is the same printed notebook a PDF would be, and the PDF is already read. Canonry reads what a file is from its bytes, not from its name, so renaming one does not get it through.
What it recognises
Two things, either of which is enough. A page OneNote exported says so in its own head, and Canonry reads that, so a .mht or a page tree is recognised whatever else is in it. And a tree of HTML pages where at least one page has its own sibling folder of embedded attachments, named after the page with _files appended, is the shape only an exported page tree produces. Either way Canonry shows you how many pages it counted before asking you to confirm the OneNote playbook; say no and it falls back to a short list of other playbooks.
What it reads
Every page becomes its own entry, with the page's own title as its name and only that page’s prose as its content. Every link to another page in the same export becomes a candidate relation, and every embedded image travels across as an attachment on the page's own entity.
The page tree carries one thing more: a page sitting in a folder named after another page is proposed as a subpage of it, with the folder tree itself standing as the evidence, since OneNote’s own export produced it rather than anything written in the page.