The most important suggestion is to ignore nearly all the advice you are getting in this forum unless it is clear that it is coming from someone who has been th

The most important suggestion is to ignore nearly all the advice you are getting in this forum unless it is clear that it is coming from someone who has been there before and not just someone who is guessing about what the best plan might be. People in this forum will vastly overestimate the value of the technically nitty gritty of whatever it is you have built because most people in here are coders that think that code is the source of all value. I can't say for sure (more on that later) but I have a very strong suspicion that this company cares a lot less about your code than they do about you and your team. You need to find someone (or some people) who have been in a similar situation before and had a successful outcome. If you don't know anyone like this then ask for an introduction to someone you don't know. It's a small world. If you work at it you get get to someone knowledgeable. Then you need to give them much more detail than you gave in this post because the specifics are going to matter a lot. It's perfectly understandable that you didn't want to get into the weeds with a public post but without the details it is literally impossible to give quality advice.