Collation change can become very messy, especially when you're upgrading at the same time. I'm sure you'll be trying out this method before doing it in production system.
Anyhow, I can suggest the following "high level" points for the implementation:
1) Generate script to create your <database> and "all" objects within the database including object level permissions. Make sure collation is not used when generating the script
2) Modify the database name, collation name and file/filegroup names if required in database creation script. Only run the database creation script at this stage on the target instance. This will create a new empty database with required collation.
3) Check the remaining database script to find any deprecated feature used in the script and modify to use 2008 R2 alternative. You will also need to check the deprecated features in the target database after the migration. See the link below for details on how to check and fix deprecated features.
4) Create all the database objects except Foreign Keys and Check constraints
5) Copy the data to new database using either bcp out/in or import/export wizard. Make sure identity insert is allowed in the data transfer for tables with identity columns
6) Apply the Foreign key and Check constraints.
7 ) If required, compare the two schema's for any differences excluding the collation.
Hope it'll help.
Knowledge is a journey, not a destiny