That's a nice thought, but speaking as someone who does IT integrations, that's ALWAYS (and rightfully so) a secondary consideration in major mission-critical integrations. A competent IT team can always port-over or cook up new interfaces to make employees' & customers' tasks easier when there is a smoothly functioning back-end in place. But you never want to create a more complicated or task-disruptive integration project than you have to, especially to preserve a user-level feature, because it's like building your beautiful house on a foundation of sand...

This is, of course, assuming that the CO/UA integration team IS competent. And that may not be a fair assumption... For reference, see the DL/NW Deltamatic/PARS integration. That not only failed to keep the best of either world during the transition itself, but actively made it impossible for customers OR employees to do their jobs in the short-term... They've still not recovered certain widely-popular features more than a year after primary integration.

The one thing I can say, from a user-level, about CO's IT team is that they've generally been very good about cranking out tools on the website and in other systems to help ease processes. And they're not overly-afraid to release highly-useful tools, even if they have some known bugs that have to be refined over time. The best we can probably hope for is that things won't get WORSE in the short-term. And after primary integration, they'll bring those past skills to bear restoring some of the better UA user-level features on top of the merged ops-level base.