0

I'm working on migrating metadata and data from one org to a clean brand new org. The purpose for this migration is because we are moving from unlimited to enterprise edition and making this change requires a completely brand new org.

For the source org, I've created a project in Visual Studio Code and pulled down as much metadata that was available to retrieve using Package XML Generator extension. It took quite awhile to run, but it finally did retrieve the metadata successfully. The only error that occurred was with ObjectTranslations and I removed that folder from the project structure and commented out the node in the package.xml.Then the metadata retrieval was successful.

Now, pointing to the target org and deploying the metadata is a whole other beast. A couple of questions around this process. First, is there a way to run test deployment validations to see if there are any errors? I'm expecting that there will be some issues moving to a brand new org. Second, when I retrieved the metadata from the source org using the package xml generator extension, it pulled down the metadata from installed packages (managed and unmanaged). All the packages will be installed into the target org before attempting to deploy the metadata. Will deploying managed package metadata cause issues? Are there other issues to be aware of when attempting to deploy the metadata to a new org? Is there another tool like Workbench that would be better to handle deploying the metadata. Purchasing a 3rd party app is not an option so I can't go that route.

Thanks.

Improve this question
1
  • You cannot deploy metadata from a package, but you can deploy metadata that references metadata from a package (e.g. you cannot deploy a package's custom object but you can deploy a subscriber field added to a package's custom object). You need to clean up so you don't have the metadata from those packages. It would have been better to just use sfdx to force:source:pull rather than use some non-standard mechanism. You then just need to install the required package's then force:source:push your metadata. Of course, you really should get all the subscriber (non-packaged) stuff into git.
    – Phil W
    Dec 4, 2021 at 16:32

1 Answer 1

Reset to default
0

First, is there a way to run test deployment validations to see if there are any errors?

Yes. Use the "check only" deployment option. This is available in Workbench, Salesforce DX, and other migration tools.

Will deploying managed package metadata cause issues?

Yes. You will need to remove these extra files before attempting to deploy.

Are there other issues to be aware of when attempting to deploy the metadata to a new org?

You might have to work with your profile metadata to get some of the metadata to align, but those will come up in the check only deployment.

Is there another tool like Workbench that would be better to handle deploying the metadata.

All of the options are pretty much the same. After all, the underlying API is always the same. Choose whichever you prefer. VS Code, Ant, Salesforce DX, Workbench, and so on. There are a ton of free options available.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .