Hi Renuka,
It doesn't look like you ended up upgrading the database, so it's not finding that column.
The 'migrate' command isn't something Review Board supports, and should not be run. The 'rb-site upgrade' command is responsible for handling all aspects of your database upgrade.
I'd have to know more about what the upgrade outputted, and how you created/prepared the database, but I can offer these suggestions:
1. Make sure that you are not trying to re-import a MySQL dump into a database that has already been populated with Review Board. You will need to completely erase the destination database, create a blank database in its place, and then perform the import. Otherwise you are mixing old and new state.
2. Make sure you have copied your old site directory to the new one. In particular, the conf/ directory's settings_local.py must be copied over (you can change the database configuration, but some other settings, like SECRET_KEY, must remain the same between installs).
3. After the import, run the 'rb-site upgrade' command. If this fails at all, then stop what you're doing, save the log file it generates, and then contact us. Depending on the nature of the problem, you may need to sign up for a support contract with us in order to fully resolve the issue. But if it's something simple where we can point you in the right direction, we will do so. Once it's in a failed state, you won't be able to resolve it by running other commands.
4. Don't run the 'migrate' command or 'evolve' command. Only 'rb-site upgrade'. The 'migrate' command runs only part of the upgrade operation, and must be managed by 'rb-site upgrade' or you risk an incomplete upgrade.
I'd suggest re-creating the database, following the above, and then being very careful to record all output and the log from the upgrade operation if it still fails.
Christian