I am now about to start re-building and old project writing in just core php (about 10 years old). The DB structure on the role is great (any amendments can be done with migrate), how can I create migrations for all databases (about 250 tables).
I believe I need to migrate the tables in, as without this i cannot use crud tools
You don’t need to create migrations in this case. Just import the database and use the crud tools to generate what you need. The migrations use after you set up the dev database to easy port the changes made on the dev db to a production db.
Of course the best is if your legacy database is innodb, then you will use the whole power of AR.
I would set up the dev version of the database and the production version from the same sql source file. I treat it as "a point zero" where you start the developing process from. After that, if some changes are being made on the dev version I would reflect it with migrations and fire the migrations on the production.
And the last sentence is repeatable: Reflect all changes on the dev db with migrations and fire the migrations on the production and so on.
I have already a production db. I have now downloaded that and an building the app in development at the moment (as of 1 hr ago).
Just so I understand. Locally i work on the development DB and make all the changes required. My client is using the old app with the production db now. Then when i am ready and it tested locally I plan to do the following.
upload app on to a dev.xx.com testing domain for client
init that app to production
apply db changes (only up not down as do not want to destroy production v1 app)
when client approves move to live root and apply down changes to db.