After upgrade all builds are queued

When upgrading from 2.0.x to another 2.0.x here's the process I follow:

1. Make new, empty database.
2. Export XML in previous version.
3. Re-deploy new Bamboo.
4. Point it at new, empty database.
5. Import the previously exported file.

As soon as the import is done, every build we have is put on the queue for an 'initial, clean' build. If I delete builds off the queue they come back on the next round of checks, so ultimately I have to wait out around 170 builds. I've tried restarting Bamboo a second time and the builds always find their way back to the queue.

Bamboo does, however, know (on some level) that it is not an initial, clean build because the previous latest build numbers are still in tact (they don't all reset to 1.)

Of secondary, and probably related, concern is the fact that after the upgrade all our build artifacts seem to be gone. All the build results, logs, etc. are there but the artifacts are physically gone from the bamboo-home\xml-data\builds\...\download-data\artifacts\... directories. Of course, the initial, clean build artifacts are there. Our artifacts have a practical lifespan of exactly one build so no big deal for us but I thought you'd want to know.

I suspect this is a product of importing to a new, clean database instead of converting/upgrading the previous one, but I always like to have a clean, simple rollback procedure in case something goes haywire (by no fault of Bamboo's, of course!)

This has happened for both our upgrades from 2.0 to 2.0.1 and from 2.0.1 to 2.0.2. Also, in helping test a snapshot build of 2.0.3 for fixes to the Perforce integration, it still does the same thing.

Thanks for listening!