Are you facing the challenge of org merges? It is complex and huge as it sounds. What to consider in the planning phase? What will be the order of subtasks? What to expect from stakeholders? What are the typical pitfalls? And what you can do to avoid future headaches when org merge is not even on the horizon? Having real life experience in org merges two times already, I am happy to share my experiences from an admin’s perspective. You will walk away with the main roadmap of an org merge project and a list of potential errors to avoid.

1. What I have learnt from org merges
- An admin’s view
by Robert Szerencses

2. #CD22
Robi Szerencses
- Salesforce Administrator @Formlabs - 3D printing
- 8 years with Salesforce
- 4 x certified
- 2 x org merge survivor
- Twitter: @RobiSzerencses
- Linkedin: /robert.szerencses
About me

3. #CD22
What?
- Combining two Salesforce instances
- Both data and metadata
Why?
- Company acquisition
- Same company but different divisions
Org merge?

4. #CD22
1. Assess the two orgs
2. Align business processes
3. Build and deploy configuration
4. Import data
5. Test
6. Go live
7. Support, support, support
A Project Scenario

5. #CD22
Continuos Documenting
- Transparency of setup and processes
- Accelerate collaboration
- You know what’s in your org
Step 0

6. #CD22
Lift and shift or optimization?
Lift and shift is:
- Quick
- Easy
The Question

7. #CD22
Org assessment
- Set roles and responsibilities for the project
- Review what’s in the instances
- Decide which will be the master org
Step 1 - Org Assessment

8. #CD22
Salesforce Optimizer - reduce tech debt
Step 1 - Org Assessment

9. #CD22
Salesforce Org Compare - for metadata
Step 1 - Org Assessment

10. #CD22
Field Trip - field usage analysis
Step 1 - Org Assessment

11. #CD22
Business Process Assessment
- Involve business decision makers
- Review processes
- Document with diagramming tools
Step 2 - Business Processes

12. #CD22
- Technical decisions to make (sharing, automation,
objects)
- Dev Sandbox for metadata
- Force.com Migration tool
- Fix errors early!
- Integration
- UAT in FullCopy Sandbox
Step 3 - Metadata

13. #CD22
- Data cleansing (duplicate or useless data)
- Legacy ID field on objects
- Parent objects first
- Start with a small sample data
Step 4 - Data

14. #CD22
- Always you test first
- Invite some key users early
- Wider range of users test in UAT
- Again: don’t forget about integration!
Step 5 - Test

15. #CD22
Step 6 - Go live

16. #CD22
- "Anything that can go wrong will go wrong."
- Keep resources available for support
Step 7 - Support

17. Thank you! #CD22