i made a bit of research and i just found out btc sha256 and btc scrypt are crosscompatible and you can even open a btcs wallet in a bitcoin sha256 client ... so my fund are not lost. In fact i could use just one wallet.dat to store btcscypt and btcsha256, both coins on it... and as it seems also devcoins. Mind succefully blown.
Coin addresses generally have nothing to do with the algorithm used to mine the coin so in theory you can use the same raw key in multiple coins and get the same address if the prefixes used in address creation and wallet export are the same, however getting at the raw key is not so easy and is encumbered by the WIF private key dump process which also adds a separate prefix. If the coin uses the same prefix as another coin then the end address will be the same.
There are a couple of exceptions to the above rule but in general the raw private key is converted to an address using the process outlined here
https://en.bitcoin.it/wiki/Technical_background_of_version_1_Bitcoin_addressesIf the prefix in step 2 (0x04) is the same in the coin then the address will be the same across coins. 0x04 is for Bitcoin.
The wallet import format also differs between coins so you may need to get the raw key depending on the coin and what prefix it uses for WIF creation during key dumping. More information is available here :
https://en.bitcoin.it/wiki/Wallet_import_formatTo create a WIF encoded key for Bitcoin you prepend 0x80 in step 2 in the above link, this may (most likely does) vary between coins.
So if the prefixes are the same when converting a raw private key to an address the end address should be identical no matter what coin you're talking about. If the key->address prefix is the same but the WIF encoding prefix is different then you will need to take that into consideration and extract the raw key from the WIF key before recreating a new WIF key.
You need to examine the source code for your coin to determine the prefixes used in address creation and WIF key creation to see if they match. If they don't then you can still convert the WIF to raw bytes and recreate the new WIF to import using the correct prefix.
Make sense ?
I suggest just importing whatever keys you can get your hands on, if doing that adds a different address to what you expect then look into converting the WIF key to raw bytes and then back into the correct format for the target coin.