Get the real story via our monthly newsletter

Search

    2
    0

rss

Send to a colleague

Home > Commentary > Trends Archive > Blog migration: your castle is your domain

Browse TrendWatch Blog

Recent Blog Entries

The Complete Archive

Trends by Vendor


TrendWatch by Channel

Web Content Management Trends

Enterprise Portals Trends

ECM Trends

Web Analytics Trends

Enterprise Search Trends

SharePoint Trends

Digital & Media Asset Management Trends

XML & Component Content Management Trends

E-mail Archiving & Management Trends


Report Excerpt

The Enterprise Social Software Report 2008 looks at... End-user interface in Traction TeamPage

"The ability to slice and dice information in various ways, comment on it, tag it, and build collaborative knowledgebases is very powerful. But this very feature-richness also makes the platform a bit daunting, especially because its somewhat dated interface doesn't always work as effectively as most competitors' to simplify your options."

(p. 233)

More about The Enterprise Social Software Report 2008

 

TrendWatch Blog

Blog migration: your castle is your domain

11-Jun-2008

One thing surprised me while evaluating hosted blog solutions for the Enterprise Social Software Report 2008: customers often indicate they'd like to switch to another service, but they keep putting it off. And it's not procrastination, it's because migration is quite an off-putting prospect.

For sure, switching software and especially SaaS-based systems is never something people look forward to. But with blog services such as TypePad and wordpress.com, migration is supposedly easy: they offer both export and import; even Blogger can be made to do an export with a couple of tricks, and if all else fails, you could use your blog's RSS feed as a last resort to grab the text and leave.

So what's the problem? Well, you can export from your old service, and probably import it to the new one. Getting the text across, or even comments and trackbacks, is perfectly feasible, but then there's the images and "other binaries." Which sounds innocent enough, but your service may host podcasts you probably worked hard enough on not to just throw away for some nice new features or better usability. How are you going to transfer all of that?

Then, a new "permalink" structure might break any hyperlinks to the blog and between posts. What if you were used to /month/day/title.html links which suddenly change to /category/title.html? And a switch of domain name might loose you your readers, not to mention your Google PageRank. Every once in a while you'll come across those http://adriaanbloem.blogspot.com addresses, and when you do, realize they're like the Hotel California: you can post there any time you want, but you can never leave the host. Not using their own domain is the #1 reason people don't switch to another service they might prefer.

You or your enterprise may embark on the adventure as "just an experiment" at first. Using one of the various SaaS options is not a bad way to go, but don't be lulled into the all-to-easy "we'll see, maybe we'll change it if it's a success." I can understand the rationale (blogging is supposed to be simple and straightforward, that's the whole point, isn't it?) but doing your homework might save you a lot of headaches.

Think through the various options. Be careful about the permalink structure you set up and where you host your images and podcasts. And remember that your castle is your domain: shell out that $10 and get a unique URL.

- Submitted by: Adriaan Bloem, Contributing Analyst

All Social Channel Trends

Join the conversation

Digg This! Search Technorati Tag it on Del.icio.us



Get a Free Sample

Wondering about CMS Watch research? Sign up to receive free samples of any of our products.




What we do

CMS Watch™ evaluates content-oriented technologies, publishing head-to-head comparative reviews of leading solutions. What makes us special?

  • Our critical analysis exposes product weaknesses as well as strengths
  • We deliver unrivaled technical depth and comprehensive project advice
  • Our research is led by international topic experts
  • We only work for buyers -- never for vendors

Contact us

CMS Watch

info@cmswatch.com

18113 Town Center Drive, Ste 217

Olney, MD USA 20832

1 800 325 6190 (customer service)

+1 617 763 5336 (int'l customer service)

Fax: +1 214 242 3048