After two half-day Org Strategy sessions that included 30 participants from 17 departments, it was decided that Recruiting populations should live in their own Salesforce Org (SF1). Separating Recruiting means that Admitted, Current, and Future student populations would then live together in a separate student-centric Salesforce Org (SF2).
The two orgs are now officially separated after a handful of remaining tasks were completed. SF2 (the new org) is up and running with the University Calendar, FLASHperks, the Salesforce Higher Ed Data Architecture (HEDA) configuration, and the Marketing Cloud Custom Subscription Center configuration. The Grad Admissions data that was previously housed in SF1 (Recruiting) has been archived. A significant amount of effort went into testing the removal of the Graduate Admission Application data and the general person data.
The final piece of the org split was reconfiguring the duplicate check rules in SF1 after the data was removed. This separation allows Recruiting business processes to be agile and able to adjust to changes in the recruitment lifecycle without impacting current student data.