I am relatively new to Wordpress, have been handed a site developed by someone else on one server, and have to deploy it to another. This site has bbpress installed, plus a load of other stuff. However it also seems to contain (somewhere) references to the other developers server, so even though I have copied the site onto my server all the links still point to his. I'm assuming that somewhere in the template files or database there is a reference to his site but I don't know where. I've done a search / replace and replaced what I can find, but still the same thing happens. I'm just wondering if there is any really obvious place I need to look for things like that. It seems to me he has just done something pretty stupid by hard coding references to his site; but maybe it's for a good reason, I don't know.
There might be hardcoded links in the theme; download it and do a multifile search with a text editor.
Editing the text dump destroys serialized data; see another Q/A here: Why is my database import losing text widget data?
To correctly change URLs in the database, use the queires below in phpmyadmin for WordPress. You will also need to change URLs in the Buddy Press tables. See Migrating a WordPress/WPMU/BuddyPress Website - interconnectit.com
If the links are hard-coded into theme files I am afraid you'd need to replace them accordingly.
If you follow what @Brady said you'd need to re-configure the options as step 3 will corrupt the serialised data in the SQL export file.
I would recommand using the WordPress OneClick Migration script. It will update site information when moving WordPress sites from server/site to server/site. It comes with detailed instruction on how to use the migration script in the Readme.md file.
Update (23 June 2011):
Disclaimer: The WordPress OneClick Migration script is written by myself and is opensource and licensed under GPL3.
There is most probably a load of references still in the database.
How I would change the references would be to do the following:
EDIT: Because I've always changed URLs from longer to shorter URLs when migrating I've never run into the issue of corrupting SERIALIZED data. If you are changing from shorter URL to longer then the above wont work but you can look at a script found here: http://davidcoveney.com/mysql-database-search-replace-with-serialized-php/
So to use the above script: