View source for TracCloudMigration

{| style="width:100%; vertical-align:top; "
| style="width:250px; vertical-align:top; padding:2px 15px 2px 2px;" | {{TracCloudTechTOC}}
| style="vertical-align:top; padding:20px 20px 20px 2px;" |
{| style="width:100%; vertical-align:top; "
<div style='text-align: center;'>
<big><b>
==Migrating from Trac 4.0 to TracCloud==
</b></div><br>

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

<span style="color:red">Important Note:</span> If merging multiple Trac 4.0 licenses into a single TracCloud license, the <b>Start Fresh</b> method is required. Only one 4.0 database can be migrated into TracCloud, meaning you do have the option of migrating one license and starting fresh with another if preferred. A complete Visit and Appointment export will be provided in a CSV format for archival purposes.

<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 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.

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. [https://wiki.go-redrock.com/index.php/TracCloudTechURL Setting up a custom URL (if preferred)]

:5. [[TracCloudMigrationFiles|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).

1st Training: Creating Centers and Groups.

2nd Training: Creating Staff, Reasons, Starting profile prefs.

3rd Training: Continuing profile prefs.

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).
<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:red">If Needed</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 (no reasons/recommendations)</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">
[[File:3150890.png|800px|Screenshot: Migration Timeline visual.]]
</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.

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. [https://wiki.go-redrock.com/index.php/TracCloudTechURL Setting up a custom URL (if preferred)]

:5. [[TracCloudMigrationFiles|Getting a copy of your Trac 4.0 database for steps 3 and 5 (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. <b>This is also the cutoff point for making additional changes to your Trac 4.0 database</b>. 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.

<hr>
<big><b>Step 4. SysAdmin Training</big></b>

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 and Groups.

2nd Training: Creating Staff, Reasons, Starting profile prefs.

3rd Training: Continuing profile prefs.

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).
<hr>

<big><b>Step 5. Final migration</big></b>

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.
<hr>

<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>

<b><i>What does it mean if something is included in the first migration, but not the second?</b> <span style="color:green">Yes</span> / <span style="color:red">No</span></i>
: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.

<b><i>What does it mean if something is included in the first *and* second migration?</b> <span style="color:green">Yes</span> / <span style="color:green">Yes</span></i>
: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.

<b><i>What does it mean if something isn't migrated at all?</b> <span style="color:red">No</span> / <span style="color:red">No</span></i>
: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.

{| class="wikitable"
! Trac 4.0 Data !! Included in First Migration? !! Included in Second Migration?
|-
| Profiles || <span style="color:green">Yes</span> || <span style="color:red">No</span>
|-
| Profile Prefs || <span style="color:red">No</span> || <span style="color:red">No</span>
|-
| System Prefs || <span style="color:red">No</span> || <span style="color:red">No</span>
|-
| Centers/Subcenters || <span style="color:green">Yes</span> || <span style="color:red">No</span>
|-

| Groups || <span style="color:red">No</span> || <span style="color:red">No</span>
|-

| Consultants || <span style="color:green">Yes</span> || <span style="color:red">No</span>
|-
| Users (e.g., SysAdmin accounts) || <span style="color:red">No</span> || <span style="color:red">No</span>
|-
| Students || <span style="color:green">Yes</span> || <span style="color:green">Yes</span>
|-
| Faculty || <span style="color:green">Yes</span> || <span style="color:green">Yes</span>
|-

| Reasons || <span style="color:green">Yes</span> || <span style="color:red">No</span>
|-
| Registrations || <span style="color:green">Yes</span> || <span style="color:green">Yes</span>
|-
| Courses || <span style="color:green">Yes</span> || <span style="color:green">Yes</span>
|-
| Sections || <span style="color:green">Yes</span> || <span style="color:green">Yes</span>
|-
| Class Schedules || <span style="color:red">No</span> || <span style="color:red">No</span>
|-


| Visits || <span style="color:green">Yes</span> || <span style="color:green">Yes</span>
|-
| Appointments || <span style="color:green">Yes</span> || <span style="color:green">Yes</span>
|-
| Availabilities || <span style="color:red">No</span> || <span style="color:red">No (Only for testing)</span>
|-

| Static Student Lists || <span style="color:green">Yes</span> || <span style="color:green">Yes</span>
|-
| Dynamic Student Lists || <span style="color:red">No</span> || <span style="color:red">No</span>
|-
| Documents || <span style="color:red">If Needed</span> || <span style="color:red">If Needed</span>
|-
| Messages || <span style="color:green">Yes</span> || <span style="color:green">Yes</span>
|-
| Resources || <span style="color:green">Yes</span> || <span style="color:red">No</span>
|-
| Resource Checkouts || <span style="color:green">Yes</span> || <span style="color:green">Yes</span>
|-

| SAGE Referral Types || <span style="color:green">Yes</span> || <span style="color:red">No</span>
|-
| SAGE Referrals || <span style="color:green">Yes</span> || <span style="color:green">Yes (no reasons/recommendations)</span>
|-
| SurveyTrac Surveys || <span style="color:green">Yes</span> || <span style="color:red">No</span>
|-
| SurveyTrac Responses || <span style="color:green">Yes</span> || <span style="color:green">Yes</span>
|-
| Q2 Configs || <span style="color:red">No</span> || <span style="color:red">No</span>
|-
| Whiteboard Rooms || <span style="color:red">No</span> || <span style="color:red">No</span>
|}

<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. [https://wiki.go-redrock.com/index.php/TracCloudTechURL Setting up a custom URL (if preferred)]

<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).

1st Training: Creating Centers and Groups.

2nd Training: Creating Staff, Reasons, Starting profile prefs.

3rd Training: Continuing profile prefs.

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).
<hr>
|}
[[Category:TracCloud]]