I'm in the same situation, where I need to convert linked clones to full clones, ideally, with no downtime.

I've seen articles where we can clone them.

However, can we storage vmotion linked clones to another datastore.  This would be going to manual full clone pool.

You can't move the linked clones in anyway to another datastore without causing problems. I just had to do this with around 100 linked clones. The only option I was aware of was to create a manual pool, shut down a linked clone, clone it to a new vm, start it, remove it from the domain, add it to the domain using the new name, and then add it to the manual pool. It was about 20 minutes of download per desktop for me over a few weeks.

Thanks for that.. What kind of problems would it cause? 

The composer service, the one that made the linked clones, tracks every aspect of where the vm is. If you move anything it will go in an error state and be inaccessible.

hmm.. our goal is to not use the linked clone anymore, as long as that VM is accessible as full clone in a manual pool.

Would the remaining linked clones be affected or just the one being moved?

That why you clone all the linked clones to full clones, and then add them to the manual pool, then you can just delete the linked clone pool and information those desktops is still intact.

was hoping to use sVmotion to save a few steps and reduce downtime

You can't storage vMotion since the linked clone disk has a reference to the replica (You can see this in the descriptor file. Reads come off the replica and writes go to the delta disk). You must do a clone.

Is cloning a linked clone to a full clone even supported?

Yes, see Converting a linked clone virtual machine to a full clone virtual machine (1026753).