The process for setting up a svn repository isn't that difficult, all the information you need is covered in the svn book. You or someone will have to commit to being the svn guy/gal, and spend some time figuring out the best repository layout, directory laytout, access method, etc. Once everything is setup you should only every have to worry about adding new users, backups and disk space.

The biggest problem you will have is the change in development philosophy within the team, many people have never used revision control or only used limited tools. If you can can foster the 'one logical change per commit' and 'a commit shouldn't (normally) break the build' philosophies, it should greatly help in the collaboration.