Use cases
The recurring ERP problems CS MeshERP is built to end, and which ERPs it reaches today.
History, files and exports should not require a custom investigation every time. These are the situations the archive is built for, and the honest state of each one.
Go back through record history
Developers can investigate changes the ERP did not explain clearly. Employees can review a readable record view and compare versions side by side, without decoding raw field-change logs.
This is what people reach for after a record changed and nobody can say who changed it, or what it said before. See Records and Timeline.
File history, built in
Browse captured file versions and changes the way you would in a cloud drive, without building a separate archive workflow.
Keeping the File Cabinet under its limit
Files are copied out of the ERP file store into the archive, keeping their original folder structure, and what is left behind in the ERP can be a stub instead of the original file.
That is the mechanism people use when ERP file storage is filling up and they would rather not delete anything. See Files for what each status means.
Proving who reached a document
Auditors ask who opened, downloaded or restored which file or record, from where, and through which channel. The access log answers exactly that, and it exports to CSV so a period can be handed over without giving anyone access to the archive itself.
Access recording is off by default and does not backfill. If an audit window matters, turn it on before the window starts. See Access log.
Leaving an ERP, or migrating off one
Keep an exported, queryable playground for reporting, migration work and the questions that come after ERP access ends.
The archive is a copy you hold. Deleted records and files are kept once captured, every subscription can export your own copy whenever you want, and read-only SQL or OData points reporting tools straight at it.
The archive keeps what was captured while the connection existed. It is not a migration tool and it does not move data into a new ERP for you. What it gives you is that your history does not stay behind in a system you are leaving.
Connector coverage today
A connector is the integration that reads an ERP into the archive, so what CS MeshERP supports and what it integrates with are the same question: the list of connectors.
NetSuite is the first connector. Which connector is built next is decided by what people actually run and ask for, and the ERPs on that list are Odoo, SAP Business One, Dynamics 365 Business Central, QuickBooks and Xero.
If you run SAP Business One, Odoo, Dynamics 365 Business Central, QuickBooks or Xero, there is no connector for it yet. Those are candidates, not commitments, and no date is published for any of them. Any system not named on this page has no connector and is not on the candidate list.
Planned, not available
These are described so the roadmap is legible, not because you can use them.
| Use case | What it would do |
|---|---|
| Integrate two platforms | Declare the sync with workflow rules that match your requirements, instead of hand building an integration each time. |
| See what an upgrade will break | Review the changes in a coming platform release that are likely to hit your customizations. |
| Catch ERP failures in your existing tools | Connect the error tracking your team already runs, so a failed script shows up alongside the rest of your alerts. |
MeshSync, upgrade highlights, data warehouse piping and error tracking connections are planned, not built yet.