Alabama.edu Migration

Shelton State is scheduled for the ACCS email migration to alabama.edu on Friday, July 26, 2024. Information about the migration is fluid at this time. Please check this page regularly for up-to-date information about this transition.

Things to Know

July 29, 2024 Update

• Setup the Outlook app for your O365 a#@alabama.edu email on your iOs device.
• Setup the Outlook app for your O365 a#@alabama.edu email on your Android device.
• To view all of your legacy Shelton State emails on a computer, visit https://outlook.office.com/mail. Log in with the new variant of your SSCC email (e.g., jdoe@sheltonstate.onmicrosoft.com) and your SSCC password.

July 17, 2024 Update

1. Please be patient during this extensive migration process. While most elements will transition smoothly, some issues may arise temporarily.
2. Your computer login has not changed. Continue to log in as usual.
3. Use your a#@alabama.edu credentials to access the Ellucian Experience/myShelton, email, Canvas, and other services. Note that Target X, Argos, and Intellicheck still require sheltonstate.edu credentials temporarily.
4. Emails sent to your sheltonstate.edu address will be automatically forwarded to your alabama.edu address. When you send emails from your alabama.edu address, they will appear to come from your sheltonstate.edu address. (Email Alias)
5. Initially, you will have access to the last 30-90 days of emails in your alabama.edu account after the conversion. The rest of your emails will populate over the following days or weeks, depending on the volume of emails in your account.
6. To view all of your legacy Shelton State emails on a computer, visit https://outlook.office.com/mail and log in with the new variant of your SSCC email (e.g., jdoe@sheltonstate.onmicrosoft.com) and your SSCC password.
7. SSCC legacy email accounts (e.g., jdoe@sheltonstate.edu) on your phone will no longer work with the previous settings. You will need to delete the old account and add a new one using jdoe@sheltonstate.onmicrosoft.com. All of your old emails will be found here until the transition is complete.
8. If you wish to continue receiving emails on your phone, you will need to add your new alabama.edu account to your device. Instructions will be provided on this site at a later time.
9. ACCS is performing a one-time copy of OneDrive concurrently with the email migration. Users must switch to the new client to add or edit OneDrive files.
10. We will get through this together.

Additional Notes from ACCS

1. 1. The email addresses for all employees, including adjuncts, will remain unchanged. Only the login credentials will be changed. Please use your alabama.edu account to log in to Ellucian Experience, Banner, and other systems.
   2. All active employees, including adjuncts, will have their email, OneDrive, contacts, and calendars migrated to their alabama.edu accounts. Older emails, prior to spring, may take several weeks to migrate.
   3. Students will retain their old email addresses as aliases on their new accounts, ensuring that any mass emails will still reach the correct inbox.
   4. Students’ institutional email aliases will continue to be added to Banner. However, students will NOT have their old emails migrated.
   5. The global address book is being modified to separate schools into their own calendars.
   6. Group emails will be set up to address the employee, faculty, and student populations collectively.
   7. Teams migration software is being purchased to facilitate data transfer. Although most teams will be ready on the cutover day, data migration will take some time, and there may be delays.
   8. Everyone will still have access to their emails, Teams, and OneDrive old environments. Nothing is going missing or being deleted. While you cannot add new items to the old environment, you will be able to retrieve existing ones.
   9. Priority should be given to using the experience portal to single sign-on with a#@alabama.edu credentials.
   10. Ensure that the email address configured in Banner matches the one being used, as this information is used to populate aliases in the new environment.
   11. Dynamic Forms will need to be modified by the NGINX running script using the data we provide.