Are you doing these steps during off hours when no one is in the system? If so that would be fine, if there's the possibility of data INSERTs/UPDATEs/DELETEs occurring during your migration window, then maybe you could RESTORE WITH NORECOVERY, then restore transaction log backups once you're ready for final cutover.
Also, something to check is if there are any SQL Agent jobs related to the databases. This is a query I use to find those:
SELECT j.job_id, j.name, js.step_id, js.step_name,
p.name as proxy_name, js.command, js.output_file_name,
CASE js.on_success_action WHEN 1 THEN 'Quit with success' WHEN 2 THEN 'Quit with failure' WHEN 3 THEN 'Go to next step' WHEN 4 THEN 'Go to step ' + CAST(js.on_success_step_id AS varchar(3)) END AS on_success_action,
CASE js.on_fail_action WHEN 1 THEN 'Quit with success' WHEN 2 THEN 'Quit with failure' WHEN 3 THEN 'Go to next step' WHEN 4 THEN 'Go to step ' + CAST(js.on_fail_step_id AS varchar(3)) END AS on_fail_action,
FROM msdb.dbo.sysjobs j
INNER JOIN msdb.dbo.sysjobsteps js ON j.job_id = js.job_id
LEFT OUTER JOIN msdb.dbo.sysproxies p ON js.proxy_id = p.proxy_id
WHERE js.command LIKE '%YourDBname%' OR js.database_name = 'YourDBname'
ORDER BY j.name, js.step_id;
Make sure you setup your database backups, DBCC checks, and any index or statistics maintenance on your new server as well.