Custom Field Migration

Trainer Name
Trainer/Consultant

PowerSchool University
2014

Agenda
Custom Fields A Little History
Legacy Custom Field Data Migration
Migrating User Custom Fields
Changes After Migration

Custom Fields - A
Little History

Legacy Custom Fields

Legacy Custom fields are created inside a Character Large Object
(CLOB). When data is stored this way it:
Is harder to access
Cannot be obtained through direct SQL
Impacts performance
In addition, legacy custom fields had other issues:
Datatypes not defined
One-to-many records not supported

Database Extensions Benefits

Supports one-to-one one-to-many and standalone tables
Allows fields to have defined datatypes
Can be based on most existing tables
Allows direct access to tables and fields from SQL
Improves performance
Includes enhanced customization features

Legacy Custom Field

Data Migration

Types of Legacy Custom Fields

Migration Process State Reporting

State and Province migrations will be on state- and provincespecific schedules.

Migration Process Activities

Activities are migrated during the PowerSchool 7.10 update to a
new table called Activities.

Migration Process PowerSchool Core

Two Sets: Core Fields and Core Fields2
Might also have State Compliance Fields
One time, irreversible process
Migration Report and Get Data are critical to avoid data loss

10

Migration Process User-Created Fields

User-created custom fields can be moved manually when new
fields are created
There is also a process to mass move user-created custom fields

11

PowerSchool Core Custom Field

Data Migration
Select the Custom Field set, run the Migration Report,
and get the data (if needed)
Back up your data and migrate the custom fields
Review the Migration Summary
Look at the Migration History

12

Select the custom field set, run the Migration Report,

and get the data (if needed).

13

Back up your data and migrate custom fields.

14

Review the Migration Summary.

15

Look at the Migration History.

16

Now Its
Your Turn

Complete Demonstration
activity 1:
Migration of PowerSchool
Core Fields Process

17

User Custom Fields

Migration

18

Three options
One field at a time: Basic Mode
One field at a time: Advanced Mode
All fields at once: Migrate Custom Fields

19

Basic Mode
Pros:
Rename the field
Add datatype
Choose which fields to migrate
Cons:
One field at a time
One Extension group

20

Advanced Mode
Pros:
Name the extension group
Rename the field
Add datatype
Cons:
One field at a time

21

Migrate Custom Fields

Pros:
Simple, one step process
Cons:
No control over the process
All in one extension group
Cant rename any fields
Cant remove any fields

22

Choose a Hybrid
Move the fields that you need to change (use Basic or
Advanced mode as needed)
Delete custom fields not needed
Migrate custom fields

23

How the Changes Affect Existing Functionality

24

Field Names

Search (1-1, not child)

List Students

Object Reports

Reporting Engine

ReportWorks

Quick Export, Export Using Template, and Date Export Manager

Quick Import, Import Using Template, and Date Import Manager

AutoComm/AutoSend

DDE/DDA

Backward compatibility is supported for the foreseeable future.

Key Points from Todays Class

Migrate core fields en masse

Migrate user custom fields using the methods that best fit
your needs
Remember that once created, custom fields in database
extensions cannot be deleted

25

Question and Answer

26

Dont Forget!!
Navigate to
http://powerschooluniversity.com
and tell us what you think!

Copyright 2014 Pearson Education, Inc., or its affiliates. All rights reserved.