Hosted PowerSchool SIS
Migration intake, secure data transfer, and reviewed hosting configuration for production PowerSchool SIS.
Move a district PowerSchool SIS from PowerSchool hosting or another provider onto k-12.cloud. The contracting customer must be the licensed institution or an authorized agent acting on that institution’s paper. Complete technical intake, accept the required agreements, and transfer the files needed to stand up the environment through a protected workspace. k-12.cloud reviews the request and records deployment configuration. Production infrastructure is not created until the request is ready and approved.
Organization admins start intake from the portal workspace.
What you get
- • District-owned hosting and migration request
- • Protected workspace for customer-provided environment files
- • Versioned authorization, terms, and SLA acknowledgements
- • Administrative review of topology, AMI, and software versions
- • Planned combined, split, or multi-application-node layouts
- • Customer data encrypted at rest with k-12.cloud-managed keys (AWS KMS) and in transit with TLS
- • No customer selection of AMI, instance type, or firewall rules
How we protect data
Customer data is encrypted in transit with TLS and at rest with keys k-12.cloud manages in AWS KMS. Storage is private — not a public bucket — so files are not readable without k-12.cloud authorization to use those keys.
How onboarding works
1. Start the request
An organization admin opens Hosted PowerSchool SIS and begins the implementation wizard from your k-12.cloud account.
2. Intake, agreements, and billing
Provide district and technical details, accept the current agreements, and finish billing through your existing organization payment method or PO.
3. Transfer protected files
Upload the files the environment needs, or submit a temporary vendor download link for server-side import.
4. Review and configuration
k-12.cloud reviews the request, accepts artifacts, and records AMI, topology, storage, and software versions. Nothing is provisioned until those gates pass.
Frequently asked
- Who can contract for this?
- The contracting customer must be the PowerSchool SIS licensee, or an authorized agent acting on that institution’s paper. Consultants and vendors cannot bring a district SIS unless they are the licensee or authorized agent of the licensee.
- Is this the training environment?
- No. Hosted PowerSchool SIS is for migrating and hosting a district SIS that may contain real student data. The training catalog item remains a separate sandbox product.
- Do we choose the AWS AMI or server size?
- No. You describe enrollment, concurrency, database size, and known requirements. k-12.cloud administrators select the approved AMI and server configuration.
- When is the server created?
- Not during this intake. The request becomes deployment-ready after files, agreements, billing, and administrative configuration are complete. Provisioning is a later step.
- How is our data protected?
- Customer data is encrypted in transit with TLS and at rest with keys k-12.cloud manages in AWS KMS. The intake workspace and the later hosted environment both store objects in a private vault — not a public bucket — so a raw copy of the files is not readable without k-12.cloud’s authorization to use those keys.