Potential issues migrating from SQL Server 2014 to 2012 by scripting tables and data? I have a very simple question.

What would be the typical "gotchas" involved with scripting all the data to migrate a 2014 SQL server database to 2012?

Is this a pretty solid process? Are there potential issues of the ordering of scripts being messed up based on FK relations and other rules?

Have there been times of "Oh man, didn't see that coming" some time later when you run into some type of conflict because of the migration that wasn't caught previously?

With business critical data, is this unwise to do? It's a cost/benefit situation of upgrading and licensing for a newer SQL.
You shouldn't have any problems scripting your database out and running it on the new database.  There isn't any data for foreign keys to affect.  After that you will have to be more careful to load the data in the correct order.  Lookup tables first, then data tables etc.

That isn't a huge issue since you can get the order down in test before trying it in production.  Where you may have your biggest problems is in any code/features that you are using that are new to 2014.  Follow the link and review the new features and search for them.  After that it's just testing, testing, testing.  Try it out in test and see what happens.  Document your changes, change them in production to remove any issues, and then start your move.