I am a Keyhotee Founder, my Keyhotee id is the number,such as "126", can I use the ID in the bitshares? If can't ,how to do with.
I've the same problem as you, my Keyhotee id also starts from a number.
As far as I know, those Keyhotee ids are not written in genesis block and then can't import.
What a sad 
BTW, is there an deadline to claim my BTSX? I want to wait the wallet more stable then claim it...
Note to Keyhotee Founders
If you have been having trouble importing your Keyhotee Founder ID it is probably for this reason:
BTSX is not Keyhotee. For security reasons, it has its own, more stringent rules for what constitutes a legal name: <ISO Basic Latin Alphabet, only lowercase alphanumeric characters, dots, and dashes. Must start with a letter and cannot end with a dash.> Think of them as far more flexible than a bank account number but constrained to facilitate accuracy and avoid name confusion and collisions.
So we tried to give an extra benefit to our Founders by including them in more than just the genesis block of Keyhotee. We added them to BTSX too.
But some names just won’t work in BTSX.
Of the names that would work, many had never been registered during the long Keyhotee registration process.
So we did what we could and included all the legal <name-public id> pairs we had.
Since so many Founders did not register (probably because of early Keyhotee instability) we decided to award Founders their BTSX shares manually.
If, your Keyhotee ID wasn’t legal under BTSX we’ll let you change it to one that you
were able to register instead. That's where your promotional BTSX will be sent. There is currently no deadline for claiming them, but eventually we will have to figure out what to do with any unclaimed BTSX that remain in our trust.
Just email
info@bitshares.org with your original Keyhotee ID and proof that you own it (either the "Founder ID" address from which you donated, or the email address you used when you signed up) and give us the
working BTSX name to which you want us to send it. That name will become your Keyhotee ID.
Meanwhile, Toast is working on a much better namespace solution that will become the common standard for all our future DACs and Keyhotee. Check his recent posts on the subject.
We apologize for the inconvenience. It is hard to keep up with how fast our technology is advancing. Our search for an integrated solution sometimes involves unanticipated compromises across multiple projects.