Hi,
If you want to make thi adapter available, I can out it on the Community Download page, just let me know when its ready.
Its really not a great idea in my opinion to populate a content management system on one machine and then move it to another. Its not so bad if the doain/hostname stays the same on the new machine but if you start on localhost/mojo and move to somedomain.com there are little issues which can cause problems and are most easily avoided by starting clean on your prodution server.
The install/upgrade system works like this.
1. If mp_Sites table doesn't exist it starts installation by redirect to /Setup/Default.aspx
2. If an unhandled error occurs it checks the current version of mojoportal core in the db in the mp_SchemaVersion table against the version reported by the code itself. If the version in the db is lower or an error happens trying to lookup the version, it directs to the /Setup/Default.aspx page for upgrade because any error is likely caused by this version mismatch and upgrading should fix it.
If the version reported in the db is the same as the code then the setup page reports that your system is up to date.
Hope it helps,
Joe
ps appolgies that it took 5 days to answer, I got busy and this one slipped below my radar at the bottom of my inbox.