1. Overview

Whilst the migration from the OUCS-provided Herald email service is being undertaken by OUCS, we recognise that there are a number of units across the university looking to migrate to Nexus from locally provided solutions. This document sets out the responsibilities of OUCS and the unit with regards to such a process.

The Nexus Email Service SLD underpins this document and states

Some departments and colleges run their own Exchange or other email service. Where a unit
wishes to migrate from their local service to Nexus OUCS will provide advice to departments
and colleges on a reasonable efforts basis, including an initial assessment of the
complexity and likely resources required to undertake any such migration, as well as
providing supporting materials relating to the preferred methods of undertaking any
migration process. However, no specific resources have been allocated for OUCS to undertake
a migration from a department service to the Nexus Service or for enabling interoperability
between Nexus and a local Exchange instance, for example. Departments wishing to migrate
from a local service or who wish to use Nexus beyond the scope of the service defined in
this SLD would be expected to commit the required resources to enable any OUCS support for
such activities (where feasible). Departments seeking a hosting facility for their own
Exchange or email service should contact NSMS in the first instance.

Up: Contents Next: 2. Outline Process

Sections in this document:

• 2. Outline Process
• 3. Migration Software/Hardware
• 4. Methods of Access
• 5. User Support
• 6. Email Routing
• 7. Administrative Access
• 8. Test Accounts
• 9. Account Provisioning
• 10. Mailboxes over 3GB
• 11. Data Types
• 12. OUCS Resources
• 13. Other Considerations