Book Image

Learning Force.com Application Development

By : Chamil Madusanka
Book Image

Learning Force.com Application Development

By: Chamil Madusanka

Overview of this book

Table of Contents (21 chapters)
Learning Force.com Application Development
Credits
About the Author
Acknowledgments
About the Reviewers
www.PacktPub.com
Preface
Index

Migrating configuration changes


As organizations make changes to one environment, those changes often need to be carried over to another environment. Configuration definitions are stored as metadata. During the development life cycle, you might want to repeatedly migrate the configurations to move or sync the changes. Migration can be done in the following two ways:

  • Manual Migration: The components that are not available in metadata API need to be migrated manually in each environment. Modifications must be repeated in every organization.

  • Metadata Migration: The components that are available in the metadata API, can be migrated automatically from one organization to another. There are a few automated ways to move metadata from one organization to another organization, which are as follows:

    • Change sets

    • Force.com IDE

    • Force.com migration tool