Hi Doc
At present, MyDataXport does not download the information into a single database.
The accounting data is exported into structured Excel and CSV files, with reports and the attachments made available through MYOB’s API saved into organised folders in the business’s own Google Drive, OneDrive, or Dropbox.
The attachments are retained as actual files rather than being embedded within a database. We also use meaningful file names and folder structures so they can be searched and matched back to information such as the transaction date, supplier or payee, transaction number and document type.
The cloud storage can, of course, also be synchronised to a local computer, server or NAS if the business wants its own local copy.
So the current output is an independent, open-format archive rather than an SQL CE database or an AccountRight restore file. MYOB remains the live accounting system.
Rebuilding an AR SE 2026.5 SQL CE file is certainly an interesting idea. I expect the challenge would be less about accessing SQL CE through Visual Studio and more about accurately recreating MYOB’s complete internal schema, relationships, identifiers, validation rules and any objects that are not exposed through the public API.
We have deliberately not gone down that path because the aim of MyDataXport is to create a durable and searchable archive that remains readable without relying on a particular version of AccountRight. Reconstructing a valid AccountRight file would be a separate and considerably different technical project.
Given your experience with the MYOB endpoints and writing your own read/write integrations, I would certainly be interested to hear what you uncover.