“svn: Revision #### not found” when trying to “svn switch --relocate” after migration

Question

I'm in the process of migrating one Subversion repository with multiple projects in it into one repository per project.

Because of copies between the projects, I had to use svndumpfilter2 to untangle them.

I ran svndumpfilter2 with --drop-empty-revs, then loaded the filtered dumpfile into a repository.

It appears that when I loaded the dumpfile into the repository, the revision numbers were renumbered. This appears to be causing a problem when I try to svn switch --relocate working copies:

$ svn switch --relocate from to
$ svn update
svn: No such revision 51000

Is it possible to get svndumpfilter2/svnadmin load to not renumber the revision numbers? Or is there a way to "switch" the revision? I tried @### on my URLs and that didn't work.

On the current subversion server:

for project in $(svn ls [repository URL]) do svnadmin dump /path/to/repos |
   svndumpfilter2 --drop-empty-revs /path/to/repos projects/$project > 
   $project.dump done

I copied over *.dump to the new server and for each project, I ran:

svnadmin create /new/path/[project] 
svnadmin load /new/path/[project] < [project].repos

Then on a working copy pointed at @HEAD on the old server:

svn switch --relocate [old repository url] [new repository url] 
svn update svn: Revision [latest revision number from old repository] not found