Migrating from CouchDB to ... ??

There is a thread/vote on LinkedIn asking "Would you consider migrating to couchbase from couchdb"
Which would be a useful and relevant data point if you thought of it as "Would you consider migrating to couchbase from another NoSQL store, e.g. couchdb (or mongoDB, Riak, etc.)"
However, given the way the question was phrased the thread pretty rapidly devolved to the usual CouchDB vs CouchBase discussion.

And that is is a bit of a trick question - CouchDB and CouchBase are different products (bear with me here).  As I allude to here  the NoSQL space is a "solution-oriented" space.  The point is that unlike the SQL space, where you can pretty much use MySQL / PostgreSQL / Oracle / whatever for *any* of your problems (money willing), in a NoSQL environment it is different.  If you've done your homework, you'll have picked the appropriate NoSQL store for your application right off the bat.  If you haven't, well, you'll probably end up switching to something else, a-la Signal.

CouchDB has a sweet-spot - and works brilliantly there.  The logical successor for CouchDB is bigcouch - which addresses back-end sharding/scaling for CouchDB brilliantly.  It is also getting rolled into CouchDB anyhow (per Cloudant). 

CouchBase is *different*.
Not better (though maybe it is).
Not *worse* (though maybe it is).
*Different*.

It has its own sweet spot.  Talking about migrating from CouchDB to CouchBase is akin to asking if people are going to migrate from CouchDB to Riak, or MongoDB, or whatever.
Could you migrate? Sure. 
Should you?  Depends.
I'd say it really, really depends on what your application does.  But it is *not* axiomatic that the migration path from CouchDB is to CouchBase.  For today at least, the migration path for CouchDB is CouchDB.