Comments on: Migration or new features? http://ilikeellipses.com/2009/04/15/migration-or-new-features/ the blog for developers who care about more than just code... Fri, 12 Mar 2010 01:01:34 +0000 http://wordpress.org/?v=2.3 By: mike hall http://ilikeellipses.com/2009/04/15/migration-or-new-features/#comment-8390 mike hall Thu, 23 Apr 2009 20:32:27 +0000 http://ilikeellipses.com/2009/04/15/migration-or-new-features/#comment-8390 For a large product, yeah, that's definitely true and I agree. I've had to deal with data migration first hand at work. It ain't fun, but it needs to be fun. I was talking more about little projects like my app, Bitter. Users may prefer getting a whole new feature rather preventing the loss of an option or a piece of saved state that is easy to get back. For a large product, yeah, that’s definitely true and I agree. I’ve had to deal with data migration first hand at work. It ain’t fun, but it needs to be fun.

I was talking more about little projects like my app, Bitter. Users may prefer getting a whole new feature rather preventing the loss of an option or a piece of saved state that is easy to get back.

]]> By: ChrisC http://ilikeellipses.com/2009/04/15/migration-or-new-features/#comment-8388 ChrisC Thu, 23 Apr 2009 20:12:10 +0000 http://ilikeellipses.com/2009/04/15/migration-or-new-features/#comment-8388 OK I see your point but the lack of some sort of smooth data migration will prevent the user/customer from upgrading. And think about who would be the most worried about loosing data. The people with the MOST data. Which means a serious user/customer. That is a lost sale/upgrade opportunity and since they are a large customer you will have to continue to support them on legacy code. Now all of this isn't the biggest deal for a small app that is just some kind of config or account info that would need to be reentered but when you are talking about large amounts of data it is a pain. Imagine if Exchange 2010 comes out and has no way of migrating your Exchange 2007 users and settings. How many people would buy that to replace an existing adoption. Microsoft would only sell to new customers and loose face with the rest. OK I see your point but the lack of some sort of smooth data migration will prevent the user/customer from upgrading. And think about who would be the most worried about loosing data. The people with the MOST data. Which means a serious user/customer. That is a lost sale/upgrade opportunity and since they are a large customer you will have to continue to support them on legacy code.

Now all of this isn’t the biggest deal for a small app that is just some kind of config or account info that would need to be reentered but when you are talking about large amounts of data it is a pain.

Imagine if Exchange 2010 comes out and has no way of migrating your Exchange 2007 users and settings. How many people would buy that to replace an existing adoption. Microsoft would only sell to new customers and loose face with the rest.

]]>