Overview
Connecticut districts can migrate Section 504 data from the legacy Connecticut Compliance pages to the Student Programs framework. The migration creates Student Program records from existing Section 504 records and establishes Student Programs as the authoritative source for future updates.
The synchronization process supports a one-way data flow from Student Programs to legacy compliance fields. This approach maintains compatibility with existing Connecticut reporting requirements while allowing districts to manage Section 504 information through Student Programs.
Migrate Section 504 Records
Step 1: Review Existing Section 504 Data
Review existing Section 504 records on the Connecticut Compliance pages before running the migration process.
The migration uses these records to create corresponding Student Program records.
Step 2: Run the Migration
Navigate to the Connecticut Student Program Migration page and run the migration process.
The migration:
-
Creates Student Program records from eligible Section 504 records.
-
Copies supported Section 504 data into Student Programs.
-
Preserves existing legacy records.
-
Prevents duplicate migrations of the same records.
The migration does not run automatically during installation; it only occurs when initiated from the migration page.
Records Created During Migration
The migration creates Student Program records for eligible Section 504 students.
Each migrated record includes the Section 504 information required by the Student Programs framework.
After migration, Student Programs become the primary location for maintaining Section 504 data.
One-Way Synchronization
Synchronization Direction
The synchronization process updates legacy Connecticut compliance fields from Student Programs.
Student Programs → Legacy Compliance Fields
Changes made in Student Programs automatically update the corresponding legacy data used for Connecticut compliance reporting.
Changes made directly to legacy compliance fields do not update Student Programs.
Student Programs remain the system of record for Section 504 data.
Synchronization Examples
Update a Student Program
When a Section 504 Student Program record is updated, the synchronization process updates the associated legacy compliance fields.
Examples include:
-
Changing program status
-
Updating entry or exit dates
-
Adding a new program
-
Closing an existing program
Update a Legacy Record
When a legacy Section 504 record is edited directly, the change remains in the legacy record only.
The synchronization process does not update the associated Student Program record.
Display of Records After Migration
Student Programs
After migration, Section 504 records display in the Student Programs interface and support ongoing maintenance through Student Programs.
Legacy Compliance Pages
The legacy Section 504 records remain available for reference and validation purposes.
The migration process does not remove historical data from the legacy compliance pages.
Connecticut districts should maintain future Section 504 updates within Student Programs rather than the legacy entry pages.
Change History
Student Programs track changes made to program records through the standard Change History functionality.
Change History supports the review of updates to program information, including entry and exit details and other tracked program fields.
Recommended Workflow
-
Review existing Section 504 records.
-
Run the Student Program Migration.
-
Validate the migrated Student Program records.
-
Begin maintaining Section 504 information in Student Programs.
-
Use Change History to review future updates.
-
Retain legacy records as historical references while using Student Programs as the authoritative source for ongoing maintenance.