HAX is easy to move content to because it is playing flat HTML files from a simple JSON based data structure. As a result the community has been able to produce a number of atypical migration methodologies. Any system we can teach to serve data in the JSON Outline Schema format that points to HTML, can be migrated to HAX.
We can convert .docx files to HTML and then taking the heading hierarchy, pull that in and build structure.
While DOCX import WILL grab images and EVERYTHING IT CAN, images are not recommended for importing. This is because they get imported as base64 content (aka a data blob in the page). This can't be optimized and the only alternative would be for us to scrub images from import (which then you'd be on this page looking anyway..)
By pointing to a public HAX site, you can import and remix HAX content in a new space. This is an OER powerhouse made possibly by the specific way HAX stores and manages data.
Notion is a great tool for managing the production process. It's a stand alone application popular about media and production teams to complete projects while generating notes and narrative around the process of producing that product. We had a faculty team using Notion to manage the production of an online course prior to deployment. Using a simple HAX import, we are able to take a Notion export and convert it to HAX.
HAX is born out of work in the ELMS: Learning Network ecosystem. The latest version of ELMS:LN effectively runs HAXcms on top of the Drupal based system and as a result can be pointed to and migrated via URL with ease. This integration primarily targets groups internal to Penn State but should work with any ELMS:LN instance.