Where should functionality be in a child theme or WordPress plugin?

Question

git

There is a large WordPress site with a lot of additional functionality (a lot of custom taxonomies and posts, a lot of ACF fields and WordPress hooks, classes have their own namespace and the vendor folder with packages updated via composer, etc.) - and all this functionality is now in the folder child topics . Naturally, all this functionality is comical in the github repository .

Is it right to keep so much functionality inside the child theme, or is it better to transfer it to a separate plugin?
This functionality will never move to any other site - it is very highly specialized and in fact if it is in the plugin and someone disables the plugin, most of the site will collapse!

Deployment to the server is still done by simply copying files via FTP
Perhaps it would be better to do a git pull in the child theme folder on the server (denying access to the .git folder inside the child theme folder)?

ps: yes, everything is clumsy and with crutches - but such a project got (((put things in order...

Answer 1

it doesn’t matter if you plan to migrate to another theme, transfer it to a plugin, if not, then it doesn’t matter where