But databases are designed to be interrogated. It's fundamental.
Of course we don't know the underlying platform, but I don't think that it would have been difficult to generate a query to find all 'Azamara' bookings, and dump those data.
This could have been done almost as soon as the purchase process commenced, and software engineers/programmers could then have processed the data, thereby avoiding the current SNAFU.
It's all very well to say that these 'transitional' kind of problems are not uncommon, but, if so, awareness of this fact, surely, should warrant proper - and timely - preparation!
I would speculate that Azamara prevaricated and that the suppliers of their new software were commissioned much too late.
Neveryheless, what seems to be interesting is that the non-web (i.e. the native interface) seems to be more-or-less intact. That suggests to me that, in fact, the data itself is not at fault, but the process of building the 'front end' has gone extravagantly, hideously, wrong!