FREE PLANNING SESSION
Meet with Metazoa engineers to discuss your project, identify potential obstacles, and explore the best approach for moving your metadata, data, and users.
Whether you’re selling a division or buying a company, start with a clear plan.
Tell us about your split, clone, or merge project. A Metazoa engineer will follow up to arrange a conversation.
WHAT TO EXPECT
We’ll review your goals and walk through a customer checklist to identify potential obstacles to your org split, clone, or merge. We will run reports that count metadata assets and data records. This helps us understand the size of the migration and discuss the effort, resources, and next steps. Plan on half an hour for setup and an hour to review the results.
POSITIVE OUTCOMES
"After a company merger, we were looking for help with our Salesforce org migration. The Metazoa team and Snapshot tooling are absolutely essential in an endeavor like this. Love it!"
Jeff McKinnis
WHAT WE LOOK FOR
We review your metadata, data, users, and destination requirements to understand the work involved in your org tranformation.
Count metadata assets and identify dependencies, code, and automation that could complicate deployment.
Count records, determine which data needs to move, and plan how to preserve relationships between records.
Identify which users need to be created or mapped, including record owners, inactive users, and permission assignments.
Check package availability, licenses, enabled features, and storage requirements for the destination org.
Identify connected systems, private reports, legacy components, and other items that may need separate migration steps.
Discuss validation, user acceptance, and the transition to the new org so the migration fits your business timeline.
Watch Metazoa CTO Bill Appleton demonstrate how shell assets simplify metadata deployment and walk through the steps for moving configuration, users, and data into a new Salesforce org.
TAKE ACTION
Use shell assets to prepare the destination, migrate your data, and deploy the full metadata. Validate the new org before bringing users on board.
Deploy shell assets to establish the destination structure and reduce dependency barriers. Resolve configuration differences before moving data.
Map users and move records in manageable groups. Use external IDs and repeat migration passes to restore relationships between records.
Replace shell assets with the full source metadata. Resolve remaining deployment errors and bring configuration, code, and automation into place.
Compare metadata, record counts, and relationships. Complete business testing and user acceptance before moving users to the new org.
Salesforce Org Splits,
Clones, and Reboots
Best practices for moving Salesforce metadata, users, and data with less risk and faster execution.
LEARN MORE
Congratulations! 
