Demo: Internal use only
JHU SAIS Admin Dashboard

Migration & Onboarding

JHU SAIS × APPLYPAL

A structured approach to moving existing ambassadors, partner universities, students and programme data into ApplyPal.

Designed for low-disruption transition

ApplyPal is designed to support migration from existing ambassador platforms through structured imports, onboarding workflows and phased rollout options. Final migration steps would depend on what data can be exported from the current platform.

1

Migration Overview

A six-step process to move from your current platform to ApplyPal.

Current PlatformExisting ambassador & student data
Data ExportCSV / structured export
ApplyPal ImportBulk import tools
Review & ValidationAdmin sign-off
Pilot Launch1–2 campuses
Full RolloutAll campuses

Johns Hopkins SAIS owns its programme relationships, ambassadors, partner university structure and student cohorts. ApplyPal can help import and organise these assets so they do not need to be recreated manually.

2

Supported Imports

Data types that can be migrated into ApplyPal.

Campuses

Supported

Campus Admins

Supported

Ambassadors

Supported

Ambassador Profiles

Supported

Student Cohorts

Supported

Schools

Supported

Programmes

Supported

FAQs

Supported

Resources

Supported

Content Library

Supported

Safeguarding Categories

Supported

Reporting Categories

Supported

Historical Conversations

Subject to export availability from existing platform

3

Migration Readiness Checklist

Steps to prepare for a successful migration.

01
Confirm current data ownership
02
Confirm export format from existing platform
03
Review ambassador profile fields
04
Map university/admin permissions
05
Upload school and student cohort data
06
Configure closed-group access
07
Configure safeguarding workflow
08
Configure retention policy
09
Configure reporting categories
10
Test pilot cohort
11
Validate admin permissions
12
Launch phased rollout
4

Phased Rollout Plan

Minimise disruption by rolling out in structured stages.

Phase 1

Pilot

1 programme
1–2 partner universities
Selected ambassadors
Limited student cohort
Validate workflows

Phase 2

Expansion

Additional universities
More ambassadors
Wider student access
Reporting review

Phase 3

Full Network

All partner universities
Full student cohort
Network-wide reporting
Research & Insights activation
A phased rollout allows Johns Hopkins SAIS to evaluate ApplyPal without disrupting existing programme delivery.
5

Data Mapping

How your existing data maps to ApplyPal's structure.

Existing DataApplyPal Destination
Ambassador profileAmbassador profile
UniversityPartner university
University staffUniversity sub-admin
Student cohortClosed group access
SchoolSchool network
FAQ / resourceKnowledge hub
Conversation topicsReporting categories
Safeguarding flagsSafeguarding dashboard
Content assetsContent library
6

Import Tools

Demo placeholders for the import workflow.

These are demo placeholders. Full import tooling is available in production environments.

7

What We Would Need From Johns Hopkins SAIS

Information required to begin the migration process.

Current ambassador list
Partner university list
Programme / cohort structure
School list
Admin user list
Desired access rules
Existing FAQs / resources
Safeguarding workflow requirements
Reporting requirements
Data export from current platform, if available
8

Transition Assurance

Our commitments to a low-risk, low-disruption migration.

No immediate full switch required
Pilot available first
Existing workflows can be mirrored
Partner universities retain familiar admin structure
Students can be invited by cohort
Historical conversations are optional and dependent on export
Current programme delivery can continue during rollout
9

Demo Migration Status

What has been demonstrated in this demo vs. how it works in production.

AreaDemo StatusProduction Approach
Ambassador importDemonstratedCSV / API import
Partner university setupDemonstratedBulk import + admin invite
Student cohort uploadDemonstratedClosed-group credentials
FAQ / resource importPlaceholderImport to Knowledge Hub
Historical conversationsNot includedSubject to export availability
Safeguarding setupDemonstratedConfigured to JHU SAIS policy
Reporting categoriesDemonstratedMapped to JHU SAIS reporting needs