TracCloudMigration
From Redrock Wiki
TracCloud Technical Documentation
Migrating from Trac 4.0 to TracCloud
If you're switching from an existing TutorTrac or AdvisorTrac 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.
Redrock's goal for all campuses is to ensure minimal downtime with minimal disruption to workflow. We work around your timeline and availability, we have migrated campuses in as little as a few weeks. For Start Fresh and FastTrac campuses, we can get you up and running as soon as we train the administrators and complete a few required integrations with your IT. The TracCloud system is structured similarly to the TutorTrac and AdvisorTrac 4.0 system, allowing your existing knowledge of TutorTrac or AdvisorTrac to give you a head start in TracCloud. Additionally, significant improvements to the interface make learning TracCloud much easier than the 4.0 system. Administrators will need to complete some follow-up tasks (referred to as "homework") after training sessions to facilitate completing the TracCloud setup process.
Important Note: If merging multiple Trac 4.0 licenses into a single TracCloud license, the Start Fresh 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.
Click here to view SysAdmin training resources.
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.
+ 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.
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.
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.