DigitalOcean is joining the Omacom Foundation as a Founding Corporate Patron, contributing $1 million a year for three years! That’s a $3 million commitment to the development, maintenance, and spread of Omarchy. What…
And then you have the updates! That’s fun! They sell ERPs as SaaS, but it doesn’t work like any other SaaS. The major updates break tons of shit because your own customizations will be based on upstream fields and methods that no longer exist. Not as bad as migrating to another ERP entirely, but not exactly cheap. At work, we keep support for our custom modules for longer than the ERP company itself supports those old versions so our customers get an extra year or 2 out of it. It’s a pretty big deal for them and of course great for us, helps retention because they’d have to spend more for less if they go to the competitors (on even the same ERP that is - going to another ERP wouldn’t just be a migration cost, the annual cost itself would go up too).
At my previous job we handled much of this in house because we were a rather large company and could do so. We ran into the same things because our bolted on processes would need to be maintained indefinitely because every ERP system update tended to break things in unspecified ways. I no longer need to do this sort of thing, but if I never have to write code for legacy IBM systems again I’ll be happy.
Can confirm, switching ERP or billing systems is a risky multi-year nightmare with a price tag that makes even larger corps blush.
And then you have the updates! That’s fun! They sell ERPs as SaaS, but it doesn’t work like any other SaaS. The major updates break tons of shit because your own customizations will be based on upstream fields and methods that no longer exist. Not as bad as migrating to another ERP entirely, but not exactly cheap. At work, we keep support for our custom modules for longer than the ERP company itself supports those old versions so our customers get an extra year or 2 out of it. It’s a pretty big deal for them and of course great for us, helps retention because they’d have to spend more for less if they go to the competitors (on even the same ERP that is - going to another ERP wouldn’t just be a migration cost, the annual cost itself would go up too).
At my previous job we handled much of this in house because we were a rather large company and could do so. We ran into the same things because our bolted on processes would need to be maintained indefinitely because every ERP system update tended to break things in unspecified ways. I no longer need to do this sort of thing, but if I never have to write code for legacy IBM systems again I’ll be happy.