To Top
Hands doing works thump_1602926366.jpg Hands doing works

TIPS FOR MIGRATING ENTIRE PRODUCTION ORGANIZATION TO A NEW PRODUCTION ORGANIZATION

Publish date:

TIPS FOR MIGRATING ENTIRE PRODUCTION ORGANIZATION TO A NEW PRODUCTION ORGANIZATION

"Migration is a process, not a problem" - Quote by William L Swing, a former American diplomat.

Migration to a new production organization is fraught with many issues and can result in unwanted speed breakers on a smooth journey.  We have assembled some tips which would be useful when undertaking such a project in the near future. Here is a list for you to keep in mind as you plan migration in the near future.

The tips are:

1. Solving conflicts. Be ready to face conflict issues such as Field references, User references, missing metadata, missing data that can arise during the migration issue.

2. Be ready to devote time to fixing hardcoded ids in Workflows, Classes, Validation Rules, and Formula Fields after the metadata and data migration is done. It can be a Record id, RecordType id, CustomField id, etc.

3. Transfer all the installed packages with the force.com migration tool. The consulting vendor is the best to gauge which of the installed packages facilitate background technical processes thus need to be migrated.

4. Prepare a schedule for testing use cases and fixing to arrive at the desired behavior (substituting hardcoded ids, making apex tests pass).

5. If migration is on the anvil, then it is best that no new development takes place in the old organization unless it is an absolute must.

6. Ensure 100% migration of everything takes place.

7. All users must shift their private reports into a public folder, in case they are required in the new production organization.

 8. Align carefully features that are enabled in the old org (e.g. Territory Management, Forecasting) and coordinate with salesforce support in order to enable or disable features in the new org in order to make it as equal as possible to the old one.

 9. Don’t deploy restrictive metadata to production before finishing data migration. You can deploy it first to a sandbox to perform tests.

Recommended read:  Steps for successful Salesforce Data Migration

We hope the above tips will make the process less painful for all concerned. If you wish to read about any topic on our blogs or contribute as a guest writer, do let us know, we will be happy to have you on board.

About the Author

author
Anand Sharma

Anand is a Salesforce Evangelist, joined the Salesforce ecosystem in 2014 helping customers to be successful with Salesforce, and joined Codleo to share the goodness with even more developers all around the world. He is based in New Delhi, with his wife, and he tries to escape summers every chance he gets.

Leave a Comment

FEEDBACK

//