TracCloudMigration: Difference between revisions

Revision as of 10:58, 20 April 2022

TracCloud Technical Documentation

• Contents

• Mail Server

• Data Import

• Data Export

• Single Sign-on

• Custom URL

• SFTP SSH Keys

• Migration from 4.0

Migrating from Trac 4.0 to TracCloud

If you're switching from an existing Trac System to TracCloud and are planning on keeping your current data, a migration process will be needed alongside general setup. You have three options of approaching this migration, depending on what will work best for your campus.

Important Note: If merging multiple Trac 4.0 instances into a single TracCloud license, the FastTrac or Start Fresh method is required. Standard Migration is not available in this scenario due to the added complexity of this migration.

FastTrac Migration - Jump to

This migration method is best for campuses with multiple licenses, or if you would like to expedite your migration to TracCloud. Only one database migration is performed, and we will work with you to setup your TracCloud instance as quickly as possible.
+ Great for campuses migrating in Summer, or during periods of low Trac usage.
+ Faster overall migration time.
- Longer period without full functionality in either Trac System.

Standard Migration - Jump to

This method is best to minimize downtime. Two separate migrations, the first to bring data into TracCloud to train with, leaving Trac 4.0 online in the meantime, and the second to bring over remaining Visits, Appointments, etc that were tracked between the two migrations.
+ Great for campuses migrating during or between semesters.
+ Minimal time without access to either Trac System.
- Longer overall migration process.
- Partial data freeze requires additional planning in advance.

Start Fresh - Jump to

No migration, and a flexible schedule. No data from Trac 4.0 will be brought into TracCloud, but we can export Visits and Appointments to a CSV file for archival purposes if needed. We will work with your SysAdmins to setup your TracCloud instance from scratch.
+ Great for campuses that want to have a fresh start with their Trac System.
+ Most flexible, as you can complete trainings and go live at any time.
- No Trac 4.0 data will be migrated into TracCloud.

FastTrac Migration

This migration method is best for campuses with multiple licenses, or if you would like to expedite your migration to TracCloud. Only one database migration is performed, and we will work with you to setup your TracCloud instance as quickly as possible.

Step 1. Planning out the migration process

Prior to any of the following steps, we'll want to schedule a quick call with you and your IT to plan out this process. This will include a general timeline for TracCloud setup, as well as migration-specific questions and planning, such as data purges or cleanups prior to copying your database.

A call can be scheduled through our website, here: https://www.go-redrock.com/help-support/request-training/

Step 2. IT Integrations

We will be working with your IT throughout steps 3 and 4 to integrate your campus services with TracCloud. This includes:

1. Setting up your mail server

2. Importing data from your SIS

3. Integrating your campus single sign-on

4. Setting up a custom URL (if preferred).

5. Configuring barcode scanners

6. Getting a copy of your Trac 4.0 database for Step 3 (if not already hosted).

Step 3. First migration

This step is where we bring as much data over as possible from your Trac 4.0 instance. Your Students, Visits, Consultants, Centers, Reasons, and more (see chart below).

Step 4. SysAdmin Training

After the data migration, we can start the training process with your SysAdmins. We will be going over the following topics (in roughly this order, and where applicable).

1st Training: Creating Centers, Reasons, and the start of your Profile Prefs.

2nd Training: Profile Prefs.

3rd Training: Creating Groups, Staff (aka Users/Consultants), and Course Lists.

4th Training: System Prefs and setting up modules (if applicable).

5th Training: Continuing System Prefs and modules, as well as addressing any final questions before step 5.

6th Training: Logging visits, using quick and batch visit utilities.

7th Training: Creating schedules and booking appointments.

8th Training: Running reports (typically a few weeks after going live).

What data will be migrated?

It's important to understand what data will be brought over from Trac 4.0. In the event that a record-type will not be migrated, it will need to be (re)created manually in TracCloud. An example of this would be Permission Groups, as there have been significant changes between the two versions, and it's not possible to create a 1-to-1 replica of a Trac 4.0 group in TracCloud.

Trac 4.0 Data	Included in Migration?
Profiles	Yes
Profile Prefs	No
System Prefs	No
Centers/Subcenters	Yes
Groups	No
Consultants	Yes
Users (e.g., SysAdmin accounts)	No
Students	Yes
Faculty	Yes
Reasons	Yes
Registrations	Yes
Courses	Yes
Sections	Yes
Class Schedules	No
Visits	Yes
Appointments	Yes
Availabilities	No
Static Student Lists	Yes
Dynamic Student Lists	No
Documents	Yes
Messages	Yes
Resources	Yes
Resource Checkouts	Yes
SAGE Referral Types	Yes
SAGE Referrals	Yes
SurveyTrac Surveys	Yes
SurveyTrac Responses	Yes
Q2 Configs	No
Whiteboard Rooms	No

Standard Migration

This method is best to minimize downtime. Two separate migrations, the first to bring data into TracCloud to train with, leaving Trac 4.0 online in the meantime, and the second to bring over remaining Visits, Appointments, etc that were tracked between the two migrations.

Step 1. Planning out the migration process

Prior to any of the following steps, we'll want to schedule a quick call with you and your IT to plan out this process. This will include a general timeline for TracCloud setup, as well as migration-specific questions and planning, such as data purges or cleanups prior to copying your database.

A call can be scheduled through our website, here: https://www.go-redrock.com/help-support/request-training/

Step 2. IT Integrations

We will be working with your IT throughout steps 3 and 4 to integrate your campus services with TracCloud. This includes:

1. Setting up your mail server

2. Importing data from your SIS

3. Integrating your campus single sign-on

4. Setting up a custom URL (if preferred).

5. Configuring barcode scanners

6. Getting a copy of your Trac 4.0 database for steps 3 and 5 (if not already hosted).

Step 3. First migration

This step is where we bring as much data over as possible from your Trac 4.0 instance. This is also the cutoff point for making additional changes to your Trac 4.0 database. Your Consultants, Centers, Reasons, and more (see chart below) will not be updated during the final migration. Data such as Visits, Appointments, etc can continue to be tracked in the meantime.

Step 4. SysAdmin Training

After the first migration, we can start the training process with your SysAdmins. We will be going over the following topics (in roughly this order, and where applicable).

1st Training: Creating Centers, Reasons, and the start of your Profile Prefs.

2nd Training: Profile Prefs.

3rd Training: Creating Groups, Staff (aka Users/Consultants), and Course Lists.

4th Training: System Prefs and setting up modules (if applicable).

5th Training: Continuing System Prefs and modules, as well as addressing any final questions before step 5.

Step 5. Final migration

This step is where we bring over the remaining data from your Trac 4.0 instance, the visits, appointments, etc that you've created since the first migration. This is also the step where your Trac 4.0 instance will be disabled, as any data recorded after this point will not be brought into TracCloud.

Step 6. Continued Training

After the final migration has been completed, we can go back to the basics to ensure you're comfortable using your new system.

6th Training: Logging visits, using quick and batch visit utilities.

7th Training: Creating schedules and booking appointments.

8th Training: Running reports (typically a few weeks after going live).

What data will be migrated?

It's important to understand what data will be brought over from Trac 4.0, what won't, and what data will be deleted during the final migration.

What does it mean if something is included in the first migration, but not the second? Yes / No

This indicates that this data will be brought over, but any modifications made to this data in Trac 4.0 after the first migration will not be reflected in the final TracCloud migration. An example of this would be Consultants and Centers, if you create a consultant/center after the first migration, it and any associated data will not be brought over during the final migration. This also applies to modifications as well. If you change a consultant's email address in Trac 4.0 post-migration, it will need to be changed again in TracCloud.

What does it mean if something is included in the first *and* second migration? Yes / Yes

This indicates that this data will be brought over during the first migration, making the data available during the training period, but will also be re-imported during the final migration to catch up on visits/appointments/etc created after the first migration. It's important to note that if you log any visits/appointments/etc during the training process (prior to second migration), this data will be lost after said second migration.

What does it mean if something isn't migrated at all? No / No

This means that this data-type will not be brought over to TracCloud at all, and will need to be (re)created manually. An example of this would be Permission Groups, as there have been significant changes between the two versions, and it's not possible to create a 1-to-1 replica of a Trac 4.0 group in TracCloud.

Trac 4.0 Data	Included in First Migration?	Included in Second Migration?
Profiles	Yes	No
Profile Prefs	No	No
System Prefs	No	No
Centers/Subcenters	Yes	No
Groups	No	No
Consultants	Yes	No
Users (e.g., SysAdmin accounts)	No	No
Students	Yes	Yes
Faculty	Yes	Yes
Reasons	Yes	No
Registrations	Yes	Yes
Courses	Yes	Yes
Sections	Yes	Yes
Class Schedules	No	No
Visits	Yes	Yes
Appointments	Yes	Yes
Availabilities	No	No (Only for testing)
Static Student Lists	Yes	Yes
Dynamic Student Lists	No	No
Documents	Yes	Yes
Messages	Yes	Yes
Resources	Yes	No
Resource Checkouts	Yes	Yes
SAGE Referral Types	Yes	No
SAGE Referrals	Yes	Yes
SurveyTrac Surveys	Yes	No
SurveyTrac Responses	Yes	Yes
Q2 Configs	No	No
Whiteboard Rooms	No	No

Start Fresh

No migration, and a flexible schedule. No data from Trac 4.0 will be brought into TracCloud, but we can export Visits and Appointments to a CSV file for archival purposes if needed. We will work with your SysAdmins to setup your TracCloud instance from scratch.

Step 1. Planning Call

Prior to the following steps, we'll want to schedule a quick call with you and your IT to plan out this process. This will include a general timeline for TracCloud setup, who we should contact for Step 2 processes, and to answer any general questions before starting.

A call can be scheduled through our website, here: https://www.go-redrock.com/help-support/request-training/

Step 2. IT Integrations

We will be working with your IT throughout the training process to integrate your campus services with TracCloud. This includes:

1. Setting up your mail server

2. Importing data from your SIS

3. Integrating your campus single sign-on

4. Setting up a custom URL (if preferred).

5. Configuring barcode scanners

Step 3. SysAdmin Training

Once your system is online, we can start the training process with your SysAdmins. We will be going over the following topics (in roughly this order, and where applicable).

1st Training: Creating Centers, Reasons, and the start of your Profile Prefs.

2nd Training: Profile Prefs.

3rd Training: Creating Groups, Staff (aka Users/Consultants), and Course Lists.

4th Training: System Prefs and setting up modules (if applicable).

5th Training: Continuing System Prefs and modules, as well as addressing any final questions before step 5.

6th Training: Logging visits, using quick and batch visit utilities.

7th Training: Creating schedules and booking appointments.

8th Training: Running reports (typically a few weeks after going live).

@@ Line 8: / Line 8: @@
 </b></div><br>
-If you're switching from an existing Trac System to TracCloud and are planning on keeping your current data, a migration process will be needed alongside general setup. This portion of our wiki will outline what this process will look like.
+If you're switching from an existing Trac System to TracCloud and are planning on keeping your current data, a migration process will be needed alongside general setup. You have three options of approaching this migration, depending on what will work best for your campus.
+<span style="color:red">Important Note:</span> If merging multiple Trac 4.0 instances into a single TracCloud license, the <b>FastTrac</b> or <b>Start Fresh</b> method is required. <i>Standard Migration</i> is not available in this scenario due to the added complexity of this migration.
+<hr style="height:1px;border:none;color:#333;background-color:#333;" />
+<div style="float: left; margin-left: 0em; width: 30%">
+<b><big>FastTrac Migration</big></b> - [[TracCloudMigration#FastTrac_Migration|Jump to]]
+This migration method is best for campuses with multiple licenses, or if you would like to expedite your migration to TracCloud. Only one database migration is performed, and we will work with you to setup your TracCloud instance as quickly as possible.
+<b><span style="color:green"><br>
++ Great for campuses migrating in Summer, or during periods of low Trac usage.<br>
++ Faster overall migration time.</span>
+<span style="color:red"><br>
+- Longer period without full functionality in either Trac System.
+</b></span>
+</div>
+<div style="float: left; margin-left: 2em; width: 30%">
+<b><big>Standard Migration</big></b> - [[TracCloudMigration#Standard_Migration|Jump to]]
+This method is best to minimize downtime. Two separate migrations, the first to bring data into TracCloud to train with, leaving Trac 4.0 online in the meantime, and the second to bring over remaining Visits, Appointments, etc that were tracked between the two migrations.
+<b><span style="color:green"><br>
++ Great for campuses migrating during or between semesters.<br>
++ Minimal time without access to either Trac System.</span>
+<span style="color:red"><br>
+- Longer overall migration process.<br>
+- Partial data freeze requires additional planning in advance.
+</b></span>
+</div>
+<div style="float: left; margin-left: 2em; width: 30%">
+<b><big>Start Fresh</big></b> - [[TracCloudMigration#Start_Fresh|Jump to]]
+No migration, and a flexible schedule. No data from Trac 4.0 will be brought into TracCloud, but we can export Visits and Appointments to a CSV file for archival purposes if needed. We will work with your SysAdmins to setup your TracCloud instance from scratch.
+<b><span style="color:green"><br>
++ Great for campuses that want to have a fresh start with their Trac System.<br>
++ Most flexible, as you can complete trainings and go live at any time.</span>
+<span style="color:red"><br>
+- No Trac 4.0 data will be migrated into TracCloud.<br>
+</b></span>
+</div>
+<hr style="height:1px;border:none;color:#333;background-color:#333;" />
+==FastTrac Migration==
+This migration method is best for campuses with multiple licenses, or if you would like to expedite your migration to TracCloud. Only one database migration is performed, and we will work with you to setup your TracCloud instance as quickly as possible.<br>
+<div style="text-align: center">
+[[File:FastTrac.png|800px]]
+</div>
+<hr>
+<big><b>Step 1. Planning out the migration process</big></b>
+Prior to any of the following steps, we'll want to schedule a quick call with you and your IT to plan out this process. This will include a general timeline for TracCloud setup, as well as migration-specific questions and planning, such as data purges or cleanups prior to copying your database.
+A call can be scheduled through our website, here: [https://www.go-redrock.com/help-support/request-training/ https://www.go-redrock.com/help-support/request-training/]
+<hr>
+<big><b>Step 2. IT Integrations</big></b>
+We will be working with your IT throughout steps 3 and 4 to integrate your campus services with TracCloud. This includes:
+:1. [https://wiki.go-redrock.com/index.php/TracCloudTechMail Setting up your mail server]
+:2. [https://wiki.go-redrock.com/index.php/TracCloudTechImport Importing data from your SIS]
+:3. [https://wiki.go-redrock.com/index.php/TracCloudTechSSO Integrating your campus single sign-on]
+:4. Setting up a custom URL (if preferred).
+:5. [https://wiki.go-redrock.com/index.php/TracCloudTechBarcode Configuring barcode scanners]
+:6. Getting a copy of your Trac 4.0 database for Step 3 (if not already hosted).
+<hr>
+<big><b>Step 3. First migration</big></b>
+This step is where we bring as much data over as possible from your Trac 4.0 instance. Your Students, Visits, Consultants, Centers, Reasons, and more (see chart below).
+<hr>
+<big><b>Step 4. SysAdmin Training</big></b>
+After the data migration, we can start the training process with your SysAdmins. We will be going over the following topics (in roughly this order, and where applicable).
+st Training: Creating Centers, Reasons, and the start of your Profile Prefs.
+nd Training: Profile Prefs.
+rd Training: Creating Groups, Staff (aka Users/Consultants), and Course Lists.
+th Training: System Prefs and setting up modules (if applicable).
+th Training: Continuing System Prefs and modules, as well as addressing any final questions before step 5.
+th Training: Logging visits, using quick and batch visit utilities.
+th Training: Creating schedules and booking appointments.
+th Training: Running reports (typically a few weeks after going live).
+<hr>
+<big>What data will be migrated?</big>
+It's important to understand what data will be brought over from Trac 4.0. In the event that a record-type will not be migrated, it will need to be (re)created manually in TracCloud. An example of this would be Permission Groups, as there have been significant changes between the two versions, and it's not possible to create a 1-to-1 replica of a Trac 4.0 group in TracCloud.
+{| class="wikitable"
+! Trac 4.0 Data !! Included in Migration?
+|-
+| Profiles || <span style="color:green">Yes</span>
+|-
+| Profile Prefs || <span style="color:red">No</span>
+|-
+| System Prefs || <span style="color:red">No</span>
+|-
+| Centers/Subcenters || <span style="color:green">Yes</span>
+|-
+| Groups || <span style="color:red">No</span>
+|-
+| Consultants || <span style="color:green">Yes</span>
+|-
+| Users (e.g., SysAdmin accounts) || <span style="color:red">No</span>
+|-
+| Students || <span style="color:green">Yes</span>
+|-
+| Faculty || <span style="color:green">Yes</span>
+|-
+| Reasons || <span style="color:green">Yes</span>
+|-
+| Registrations || <span style="color:green">Yes</span>
+|-
+| Courses || <span style="color:green">Yes</span>
+|-
+| Sections || <span style="color:green">Yes</span>
+|-
+| Class Schedules || <span style="color:red">No</span>
+|-
+| Visits || <span style="color:green">Yes</span>
+|-
+| Appointments || <span style="color:green">Yes</span>
+|-
+| Availabilities || <span style="color:red">No</span>
+|-
+| Static Student Lists || <span style="color:green">Yes</span>
+|-
+| Dynamic Student Lists || <span style="color:red">No</span>
+|-
+| Documents || <span style="color:green">Yes</span>
+|-
+| Messages || <span style="color:green">Yes</span>
+|-
+| Resources || <span style="color:green">Yes</span>
+|-
+| Resource Checkouts || <span style="color:green">Yes</span>
+|-
+| SAGE Referral Types || <span style="color:green">Yes</span>
+|-
+| SAGE Referrals || <span style="color:green">Yes</span>
+|-
+| SurveyTrac Surveys || <span style="color:green">Yes</span>
+|-
+| SurveyTrac Responses || <span style="color:green">Yes</span>
+|-
+| Q2 Configs || <span style="color:red">No</span>
+|-
+| Whiteboard Rooms || <span style="color:red">No</span>
+|}
+<hr style="height:1px;border:none;color:#333;background-color:#333;" />
+==Standard Migration==
+This method is best to minimize downtime. Two separate migrations, the first to bring data into TracCloud to train with, leaving Trac 4.0 online in the meantime, and the second to bring over remaining Visits, Appointments, etc that were tracked between the two migrations.<br>
 <div style="text-align: center">
@@ Line 74: / Line 241: @@
 <hr>
-==What data will be migrated?==
+<big>What data will be migrated?</big>
 It's important to understand what data will be brought over from Trac 4.0, what won't, and what data will be deleted during the final migration.<br>
@@ Line 156: / Line 323: @@
 |}
+<hr style="height:1px;border:none;color:#333;background-color:#333;" />
+==Start Fresh==
+No migration, and a flexible schedule. No data from Trac 4.0 will be brought into TracCloud, but we can export Visits and Appointments to a CSV file for archival purposes if needed. We will work with your SysAdmins to setup your TracCloud instance from scratch.<br>
+<div style="text-align: center">
+[[File:9498519.png|800px]]
+</div>
+<hr>
+<big><b>Step 1. Planning Call</big></b>
+Prior to the following steps, we'll want to schedule a quick call with you and your IT to plan out this process. This will include a general timeline for TracCloud setup, who we should contact for Step 2 processes, and to answer any general questions before starting.
+A call can be scheduled through our website, here: [https://www.go-redrock.com/help-support/request-training/ https://www.go-redrock.com/help-support/request-training/]
+<hr>
+<big><b>Step 2. IT Integrations</big></b>
+We will be working with your IT throughout the training process to integrate your campus services with TracCloud. This includes:
+:1. [https://wiki.go-redrock.com/index.php/TracCloudTechMail Setting up your mail server]
+:2. [https://wiki.go-redrock.com/index.php/TracCloudTechImport Importing data from your SIS]
+:3. [https://wiki.go-redrock.com/index.php/TracCloudTechSSO Integrating your campus single sign-on]
+:4. Setting up a custom URL (if preferred).
+:5. [https://wiki.go-redrock.com/index.php/TracCloudTechBarcode Configuring barcode scanners]
+<hr>
+<big><b>Step 3. SysAdmin Training</big></b>
+Once your system is online, we can start the training process with your SysAdmins. We will be going over the following topics (in roughly this order, and where applicable).
+st Training: Creating Centers, Reasons, and the start of your Profile Prefs.
+nd Training: Profile Prefs.
+rd Training: Creating Groups, Staff (aka Users/Consultants), and Course Lists.
+th Training: System Prefs and setting up modules (if applicable).
+th Training: Continuing System Prefs and modules, as well as addressing any final questions before step 5.
+th Training: Logging visits, using quick and batch visit utilities.
+th Training: Creating schedules and booking appointments.
+th Training: Running reports (typically a few weeks after going live).
+<hr>
 |}

TracCloudMigration: Difference between revisions

From Redrock Wiki

Revision as of 10:58, 20 April 2022

TracCloud Technical Documentation

Migrating from Trac 4.0 to TracCloud

FastTrac Migration

Standard Migration

Start Fresh