Guides / ERP augmentation
Nothing about ERPNext is hiding your data. The whole product is open, which is most of why you picked it. The cost shows up somewhere else: every answer beyond the built in ones needs somebody technical, and in most operations running it that's one person.
If you're on ERPNext you already know the pitch that got you here. Nothing per seat, nothing locked away, host it wherever you want, change anything. All of that is true, and it's a genuinely good position to be in. The bill arrives in a different currency.
It's worth being clear about how much better this is than the alternative, because it's easy to lose sight of once you're living with it.
Plenty of manufacturers are running systems that publish nothing at all for an outside developer, or that need a paid certification course before the vendor will even help. On ERPNext, everything is documented, the data model is right there, and there's a large active community. Nobody has to buy anything or ask permission to find out what's possible. That comparison across fourteen systems is in which ERPs let you get your data out, and ERPNext is at the open end of it.
So this note isn't about a wall in the software. It's about what happens when the only thing standing between you and an answer is technical time you don't have.
None of that is a knock on the software. It's what self hosting an open system costs, and most operations that chose ERPNext knew they were signing up for some of it. The question is whether it should keep costing your one technical person their week.
Nothing moves and nothing gets replaced. ERPNext stays your system of record, hosted exactly where it is. What gets added sits alongside it and reads.
The honest version of the pitch is that this is work your own person could do. What you're buying is that it gets done, stays done, and stops depending on one calendar.
The connector I've built and run in production is for a different manufacturing ERP, into QuickBooks Online, at a real manufacturer, in daily use. That's the one with real scars on it. The ERPNext connector is already built against what ERPNext publishes. No operation has run it on live data yet, which is the part that matters.
That's worth saying plainly to this audience in particular, because you'll check. Every serious fault in the connector that is in production showed up only against the customer's real data and was invisible in every test beforehand. Open documentation gets you most of the way. The rest is found by pointing it at a real operation.
So the first ERPNext operation to run this gets design partner terms. Being first is worth something and I'd rather price it that way than pretend otherwise.
A paid Diagnostic first, where I look at your install, your customizations and the questions you keep chasing by hand, and establish what your data can honestly support. Then a Build quoted up front, so you know the price before it starts, with no hourly billing. I host it and keep it running, with an ongoing care plan covering hosting, monitoring, fixes and adjustments as your operation changes.
One limit worth knowing: this reads what your operation actually recorded. If something isn't being captured, or is captured in a field somebody repurposed two years ago, no amount of connecting invents it. Finding that out is usually part of the value.
That's a design decision rather than a given, and it's one of the first things worth settling. There's normally a route that fits how you already run it, and I'd rather establish that early than assume it.
They probably could, and if they've got the time and it'll be maintained, they should. What usually tips it is that this is the work that keeps getting bumped for something urgent, and that one person is already the single point of failure for the whole system. If they want it, that's a good outcome and I'll say so.
Not by default. I read, and I don't write back unless you specifically want that, and even then it's a separate and much more careful conversation. Your customizations stay yours.
They're the interesting part rather than a problem. They're also why a generic answer about ERPNext is wrong for your install. Working out which fields your operation actually relies on is part of the Diagnostic, and it's often the first time anyone has written that down.
Related reading. If you're comparing how open your system is against others, that's which ERPs let you get your data out. If you're weighing ERPNext against the other open option, the companion note is Odoo reporting.
First call's free. About 30 minutes, a straight conversation about how your operation really runs and which answers keep waiting, not a demo. If there's something worth building, I'll say so; if there isn't, I'll say that too.