Is someone familiar with the experience of replacing systems based on 1C? What are the pitfalls?

Question

1C

We (so far theoretically) plan to replace the 1C-based system with a new development without using 1C. Has anyone already experienced this? Can we modify the 1C base for our solution to work, so that we migrate our data and the new system will work on this modified base? Does this violate the 1C license?

Answer 1

we plan to replace the 1C-based system with a new development without using 1C. Has anyone already experienced this?

Yes. Self-written bookkeeping on Fox-Pro and Access
Export to Excel and import to anything - what's the problem?
But why? The firm will be tightly tied to one programmer.

Answer 2

What for? The lion's share of tasks is solved by means of 1C many times faster than in any other way.
It is difficult to advise something without knowing the motivation for leaving 1C.
If, for example, there is a task to save on licenses, then it is really possible to transfer part of the functionality into something simpler. In the Internet there are examples of real economy of licenses.
1C http services do not yet consume licenses for each connection. You can write a simple client that communicates with 1C via an http service.