Thanks for getting back to me. Sounds like an interesting challenge. Amongst all the pain I hope you are being successful along the way.
In case it helps I’ll try to answer some questions and fill in some blanks.
Octopus isn’t “project-centric” like some other applications. That’s both an artifact of history, and it’s a bit of a differentiator with pros and cons. It means you can easily share a similar Variable, Certificate, Deployment Target, etc between multiple projects and environments. This comes with the downside of making export/import really difficult. It also means when you delete a project we can delete everything “owned” by the project, but we don’t touch anything which can be shared outside the project. We are considering changes over time where certain resources like Lifecycles, Certificates, etc can be “owned” by a project limiting their scope… but that’s not something on our immediate radar.
One of my favourite features of Octopus nowadays is “spaces” which do create fully self-contained “mini Octopuses”. You can create a space for a logical set of Projects, Environments, etc, and delete them all in one hit.
One idea instead of developing your fully tenanted solution in another Octopus Server instance, would be to upgrade Octopus, create a new Space, implement your fully tenanted solution, and move your team over to it.
The data migrator supports a “partial-export” feature where you can select one or more projects and export those, or parts of those. I would highly recommend upgrading if you want to continue using the data migrator so you get all the bug fixes we’ve shipped recently. They may not affect you, but it would be better to be safe than sorry.
If you are planning to renew your license, and it’s something of a certainty, we can probably send you a custom trial license so you can start work in the meantime. This is much easier if you have a quote generated in our purchasing system - this avoids a lot of risk on both sides.
Hope that helps!