A 20-year-old instance. A small, mighty team that inherited a mess. A hard fork ahead: refactor the Frankenstein, or stand up a fresh Encompass 3 and migrate. Before you choose, let's see it — both the current state and the future state.
Before we propose anything, here's the picture we heard on the call. If we've got it right, the rest of this page is where we'd take it.
APIs, customer portals, client portals, ETL to the warehouse — all interconnected. Any move to a new instance means making all of that polymorphic and adding abstraction layers. Not horrendously complicated, but another thing that has to be refactored.
Dev, UAT, and Prod were out of sync. Within the next couple weeks they'll all share the same schema. That unblocks safe change — it doesn't by itself tell you which change to make.
4 full-time engineers + ~3 QA, led by a director. The IT governance / Silver-Compass model is only ~3 years old; before that, the business made its own architectural choices for two decades. The team is small but mighty — and every production issue still pulls them off the work you actually wanted them to do.