Migrating to Series25 SaaS Environment Checklist
This document is intended to be used by existing Series25 customers who have a Database at Customer Site
(DBCS) environment and are migrating to a Series25 Software as a Service (SaaS) environment.
Listed below are the tasks you and CollegeNET must perform to accomplish this migration. For assistance in
performing any of these tasks, see our extensive documentation resources available from the Series25 Customer
esources portal or contacstupport@collegenet.com
Step
Your school...
CollegeNET...
Phase I - Planning
1
Signs SaaS contracts and contacts Series25 Account Manager to
schedule implementation planning call.
2
Conducts your
implementation planning call
& sends migration
questionnaire to gather
information about your
current Series25 DBCS envi
ronment.
Phase II - Data Gathering
3
Fills out and returns migration questionnaire via e-mail to Account
Manager.
4
(Optional): Remove older event cabinets after archiving database
backup.
5
DBA runs referential integrity scripts and clear out database
orphans.
6
DBA takes “Initial Snapshot” of Series25 production data and
uploads to CollegeNet FTP. SQL customers should send .bak file,
while Oracle customers should send .trx file.
7
(Optional): If planning to enable LDAP or Shibboleth at the time of
final migration, enables and tests authentication first in local
Series25 environment. Then, sends support@collegenet.com r25-ld
ap.ini file or Shibboleth attributes for set-up in SaaS environment.
Also, sends Account Manager the test LDAP or Shibboleth account
for future support access.
Will be done after the final
migration
8
(Optional): If migrating custom reports, uploads .zip of report files to No custom reports
CollegeNet FTP. These reports would be found in the cust folder of
your Resource25 installation.
9
(Optional): If any SQL or direct Series25 database queries/reports or Sent Web Services query and
documentation
custom integration are used locally, school rewrites them in
WebServices.
Phase III - SaaS Environment Build-out
10
Uses data sent via FTP to
build Series25 SaaS
Environment.
Any relevant information
found during the test
database import (e.g.
orphans, data corruption) alo
ng with solutions will be sent
to school. School DBA
should resolve any issues
prior to final migration.
11
Creates active R25 user
names as Citrix users. This
allows existing R25 users to
log into Citrix using current
R25 username, using a
generic Citrix password we
create for your school.
12
Sends Series25 SaaS
Environment credentials.
Note: Your hosted
environment will have a new
user account, service25.
Please leave this account
active, in the administrator
security group, and don't
change the password.
Phase IV - SaaS Environment Testing
13
DBA resolves any import errors sent by CollegeNet Technical
Analyst.
14
-New server set up
IT Upgrades to Series25-SIS Interface version 3.4. Or, if
Datatel-Colleague school, install and test SaaS Interface Connector,
-Request to open up firewall
using instructions on wiki at SaaS Interface Connector
to be complete on 7/24/14
15
Tests Series25-SIS Interface (or SaaS Interface Connector) by
completing a batch load, watching a course move via transactional
processing and sending a course from Series25 SaaS to SIS.
16
Functional Administrator shares Citrix link and 25Live access with
Series25 users.
17
Series25 users test their ability to log into R25i (via Citrix) and
25Live (via web browser). Users should test typical tasks (.e.g
creating/editing events, running searches, generating standard
reports, sending e-mails, etc).
18
(Optional): If enabling LDAP or Shibboleth, tests connectivity to
hosted SaaS environment via 25Live and possibly R25.
19
(Optional): If using SaaS R25 WebViewer, test it. Makes sure the
URL is working to verify WebViewer connectivity, browse
WebViewer events and enters test request(s).
20
(Optional): If migrating custom reports, test these reports.
21
(Optional): If any SQL or direct Series25 database queries/reports or
custom integration have been rewrote in WebServices, tests this
functionality.
22
(Optional): If Schedule25 is licensed, test Schedule25 run. Follow
guidelines for server-side file saving for Schedule25. See wiki page
Setting up SaaS Schedule25 Run File Locations
23
E-mails Account Manager to indicate successful completion of all
SaaS environment testing steps. Or signs this task list to indicate
successful completion of all previous tasks and sends to Account
Manager (see below).
Phase V - Final Migration
24
Choose final cut over day. We are able to migrate Monday through
Thursday of each week. School should send final database
snapshot night before date of final migration (if possible). No users
are allowed to access your local Series25 products after the
snapshot is taken and should wait until the SaaS environment has
been released, then begin entering Series25 data into the SaaS
environment. Expect up to 48 hours of downtime during migration.
25
Schedule final cut over day by e-mailing support@collegenet.com (c
c'ing your Account Manager) the date/time for your migration.
Support will confirm the reservation of this date based on current
availability.
26
DBA takes "Final Snapshot” of Series25 production database and
uploads it to CollegeNET FTP at scheduled migration time.
27
IT turns off all access to Series25 products on campus, so that no
one can enter data into Series25 DBCS environment. Also disables
CRON and any automatic DB backups.
28
Uploads final snapshot of
Series25 database into new
SaaS environment. Once
complete, technical analyst
will e-mail your school and
users may begin using SaaS
environment.
29
IT enables CRON. Points test and production Series25-SIS
Interfaces at SaaS environment. Confirms interface testing steps
once more.
30
Users begin entering data solely into SaaS environment.
31
Migration complete.
Customer Signature:
CollegeNET Signature:
© 2013 CollegeNET, Inc. August, 2013
Date:
Date: