Not with a simple migration (like a vMotion).
You can stop the source vApp - add it to a public catalog... then from the other org spin up a copy of that catalog item in the new location.
Some other tricks exist, but they have limitations (or can be a pain) - for example you could use vCenter to clone each of the VMs in the current vapp to a temp location - then from vcloud import those copied to a new vapp in the new org location.
