I assume that Reginald's complain was not about the data itself, but about the fact that he will now have to move his blog elsewhere - the drag of setting it up, and making sure that everyone can find it.
Any major platform has import tools from the other large platforms.
In fact, it's ironic that Posterous once wooed users by building simple import tools to pull in data from Wordpress (among others). Now, people are using Wordpress's import tools to pull their Posterous blogs back into the WP platform.
If you have your own domain name set up, rather than a free subdomain tied to the blogging platform, there is no issue of worrying about people finding you. Same goes for using RSS if you use Feedburner or have your feed available at a standard location on your own domain.
In addition, there is the problem that links from other websites to your blog will stop working, and your Google search rankings will be affected.
I have a custom domain name for my Posterous blog, so links to the main site will not break, but links to individual posts will break if the new blogging platform doesn't follow the same link naming convention as Posterous (which most likely they don't)
Do you guys have any ideas/tricks how I can avoid issues like the above, and how to make sure that certain posts which currently rank high in Google search results keep their rank, if possible?
You can create a set of 301 redirects to make sure traffic that is sent directly to a given post finds the correct page. It will also let search engines re-index your content at the new address.
You can do this by dumping the relative paths of your previous blog posts and current ones into your .htaccess file. This won't get all of the old links (category/tag links, for instance) but at least direct links to a specific post will end up in the right place.
I guess the only way to accomplish that is to set up the new blog on my own server where I will have access to a .htaccess file. That is, I can't use any hosted blog like blogger, tumblr, wordress.com. Is this correct, or are there any hosted blog services that will give you this fine-grained control? Or are there any things I can do on the domain registrar side?
Alternatively, is it a good or bad idea to route all traffic to my blog through a VPS I have, so that all the old blog post addresses go to the right place on one of the hosted blog services? (I'm just trying to avoid hosting my own blog, since I assume there are a lot of headaches involved)
I decided a while ago to move my personal site from Posterous to GitHub pages [1]. It's been a little tricky to set up but only because I'm fussy and haven't messed with css before. Still not finished since I can't find a sensible way to extract my content from Posterous (that dosen't involve the API).
With GitHub pages, you don't need to worry about the hosting aspect and you'll always have a copy of your site locally. Pretty sure you can deal with the .htaccess file stuff too.
If you decide to look into this, check out Jekyll-bootstrap too [2].
I moved mine from Tumblr to GitHub recently and used a migration script to grab all the posts and turn them into Markdown files. There's a script that works with Posterous too: https://github.com/mojombo/jekyll/wiki/blog-migrations
edit: I've just realised I don't need the code to be merged into jekyll in order to use it (facepalm).
edit2: ok, maybe not as straightforward as I thought. I'm not really a coder so it takes me longer to understand what scripts are doing (and then tweak them so they work for me).
Routing all blog traffic through your VPS is a bad idea, IMHO. Your VPS becomes a single point of failure for your blog - if it stops working all of your posts are unavailable, not just the ones that require 301s.
