You can move all of the Salesforce organization’s metadata components to a GIT repository branch using the Salesforce Bulk Migration TaskOpsera enables you to perform metadata migration using the Salesforce Bulk Migration Task. You can use this task to migrate all the metadata components available for the selected component types from Salesforce Org to Git branch.
Workflow
To start the migration, a Salesforce Bulk Migration needs to be created as a task. Once the task has been created, run it to select the metadata component types and the target branch to bring in the changes. Opsera will push the code to the configured branch of the repository during complete sync-up and override any components that are present there. You can view the logs once the Salesforce Bulk Task has been triggered.
...
In this section:
Create Salesforce Bulk Migration Task
Run Salesforce Bulk Migration
View Task Activity Salesforce Bulk Migration Logs
Create Salesforce Bulk Migration Task
...
Navigate to Tasks and open the created salesforce bulk migration task.
Click Run Task.
In the Opsera Task Confirmation popup, choose to create a branch or select an existing branch.
Use Existing Branch: To use an existing branch, select from the Branch dropdown.
Create a new branch: To change the branch where the files are getting synched by creating a new branch, toggle Create a new branch to on. Provide a branch name and select an Upstream Branch from which the feature branch will be created.
4. Click Run Task.
5. In the Salesforce Bulk Migration Wizard popup, click Start a New Instance.
6. Select the component types and click Proceed with Selected Components.
...
7. Under Salesforce Bulk Migration Wizard Confirmation Screen, verify the components selected and click Proceed.Â
View Task Activity Logs
View the Task Activity Logs once the Salesforce Bulk Task has been triggered and is running to see the components that were retrieved and the total count against each component type. To view the console log, locate the Run number you want to monitor and click console log in the Log Type column.
...