[SalesForce] Salesforce Org to Org Object migration

Moving out of your Packaging Org. You will eventually reach a point where what you have extract is a unmanaged version of your package contents, which can be made to be compatible with a subsequent deployment back to your packaging org, which i'm guessing is what you have later in mind? I have done this before, when I've out grown developing in a packaging org, but rather I've done it with a view to populating a source control system and using that as the central definition of truth for my app.

Developer Workflow from Source Control. You can still use your sandbox orgs for your developers, but have them deploy using the Salesforce Migration Toolkit from your source control system. When your ready you can do a deploy to your packaging org from source control.

Validating Source Control Contents. Note that you can extend this to a continue integration build approach and effectively use the test deploy aspect of the toolkit to confirm your current state of source control is compatible with your packaging org (without actually committing to it until your ready).

We are using DevOrgs with different namespaces as part of our development process. I have described parts of it as an answer to Best practices for Versioning managed packages in Git. In our experience it is the best to:

1. Never hardcode references to the namespace in your code. If the namespace is really needed, it could be determined by a custom object or field of your package and comparing getName() vs. getLocalName()
2. Use a branch or something similar to separate your DevOrgs with different namespaces.
3. Replace the namespace reference at the package.xml by something generic like <namespacePrefix>PREFIX</namespacePrefix> and replace it before deploy and after retrieve. The real namespace could be stored at the build.properties file
4. Create a unique namespace for the target DevOrg before the first deployment and put it into the build.properties. We are using our JIRA story keys for that (e.g. FOO-2346 key results in FOO_2346 namespace).