We’re Here to Help!!

Find A Solution, Learn Best Practices & Get Support 24x7

Data Migrator Implementation Guide

Follow

Release Management
Implementation Guide

Index

    Core Setups
  • 1Overview
  • 2Installing Flosum
  • 3Setting up Flosum integration user
  • 4Connecting sandboxes to Flosum
  • 5Setting up users in Flosum
  • 6Setting org permissions
  • 7Decide on naming convention
  • 8Initialize the repository
  • 9Setting up workflow permissions
  • Application Development Flow
  • 10Pulling changes from dev sandboxes
  • 11Branching strategy
  • 12Conflict and Merge strategy
  • 13Static Code Analysis
  • 14Apex
  • 15Regression testing
  • 16Reference Architecture
  • Integrations
  • 17Jira
  • 18TFS/Azure Devops
  • 19Git Integrations
  • Compliance & Governance
  • 20Compliance & Governance
Implementation Guide from Data Migrator
Data Migrator is an ISV application that should be installed in your Production organization (or the organization which has the data to be exported). Data Migrator uses the current installed organization as the source organization to extract the data and pushes the data to the target organization.

For more information about how Data Migrator works, check out our User Guide.

To install the application, click here. 

Data Migrator does not store the credentials of the target organization. Data Migrator will always prompt for credentials during every migration.
Print Friendly and PDF
Was this article helpful?
0 out of 0 found this helpful

Comments