From my limited experience with the schildbach wallet, you would export the key, but it would be encrypted via a password. You would need to use openssl via the command line to decrypt the private key before importing into another wallet. It's possible, but I doubt a lot of people are going to know how to do it. We could provide instructions via the main site though for these users.
If the airdrop went to paper wallets, then even better. That's a slam dunk.
Ultimately, an updated schildbach wallet would be optimal. It's on my list of things to investigate, but I will say that I'm in no way, shape, or form an android developer. I've started porting the dgb wallet over, but there are redundancies in the code that have me a little confused. Essentially, all the new schildbach wallets today are built on another coins wallet, that was built on the digitalcoin wallet, which was modified by hashengineering and Ahmed Bodi, which was a port of the original. There are a lot of ownership changes there that all added their own code to their individual projects. I need to sort out what's needed, and what's redundant. We ran into the same thing with the traditional client. We took out a handful of functions and variables that did absolutely nothing but reference themselves. I suspect the schildbach wallet will be similar.