Considering I asked for constructive criticism, "it sucks" is far from it, and doesn't help me. I'll hear all negative viewpoints (and this is exactly what this thread is for) but the only way I can improve is if you can get your opinions out without being overly emotional about them. The forum is standalone, meaning, you can log into the forum without relying on the network other than uploading new music. But the process of uploading music should be near flawless by now. However, this is the reason why we kept the archives open until recently.
The sequence of events that led to where we are now, was a little more complicated than you think, but I will try to explain. I made the decision to convert over to IPB because vbulletin at the time was far behind IPB in terms of architecture (I got my tips from Mike). I did not want the developers to develop the network with an older vBulletin architecture, because vBulletin was a few months behind a major overhaul of code. This would most likely have made upgrading vBulletin nearly impossible without breaking the network integration. Essentially, we would have been stuck with an older version of Vbulletin for quite some time, and this would have been bad for security updates. Thus, this is the main reason why we switched to Invision.
When the developers were ready for the user integration, we put the forum on a subdomain so that the forum could seem like a standalone. We did have a test site tested by a few members, but when you introduce people at a large scale, things that no one could have predicted begin to happen. So while all kinds of things were happening on the network, the forum for the most part remained untouched. And integrating accounts takes time (and money). To have the developers integrate all accounts for 7000+ members on a test site, then to do it again on the live site, would have cost me more hours than necessary. Like it or not, the best way to get people testing at a large scale is by introduction, little by little.