Hi Chris,
Unfortunately those review requests are going to be bound to the old repository... This is a pain point for sure, and we have thoughts on how we might eventually address this to allow effectively archiving the source files for a repository that are used in diffs so a repository can be retired.
Right now, the best and only viable option is to keep the CVS server around somewhere and point Review Board to it.
If you want to update everything to use the SVN repository instead, you're going to need to:
1. Go through every uploaded set of diff data and re-write the diffs to be compatible with a Subversion diff posted against the appropriate repository. This is error-prone, and you'll need to check up to three tables for this data (you might have old diff content in diffviewer_filediff, and then there's diffviewer_filediffdata from Review Board 2.5 and diffviewer_rawfilediffdata from 3.0+).
2. That will change the SHAs of the diff content, so you'd need to rewrite any references in diffviewer_filediff tables to point to the new SHA instead of the old one.
3. You'll also need to update that revisions and paths on all diffviewer_filediff entries, so Review Board can locate those files from the correct repository.
4. You'll then need to update the repository entries themselves to point to the Subversion server.
There might be all sorts of other things I'm not thinking of... It's extremely error-prone. Doable in theory, but a lot of work. It'll take some trial and error. Definitely experiment with a test copy of the database, not the production one :)
Personally, I'd keep the CVS server around if at all possible for now.
Christian