Presentation from Salesforce.org Higher Ed Summit 2018 by: Mike Muhlfelder, Jitterbit, Taylor University. Join Sue Ours of Taylor University and Mike Muhlfelder of Jitterbit as they share a migration story to HEDA. Learn about: -How Taylor University transformed their organization -The process Taylor University used to evaluate HEDA and a potential migration -The build behind the data migration to the new Salesforce HEDA org -The user testing and preparation they underwent before migrating -Lessons learned and experiences on being a new HEDA user Watch a recording of this presentation: https://youtu.be/f7AvYqM8LFI

1. Taylor University: A HEDA
Salesforce Success Story
Mike Muhlfelder, VP of Sales, Jitterbit
Sue Ours, Enrollment Management Systems Administrator,
Taylor University

2. © 218 JITTERBIT | 2
50K
Global users
#1
Customer satisfaction
141K Endpoints connected
105% Net revenue retention
75% Go live in under 30 days
Gartner® Magic Quadrant™ leader
90% Of customers achieve ROI in <12 mos.
Jitterbit Overview
Salesforce Relationship
Gold Partner since 2007
— Only integration vendor that is
HEDA Core Compatible
— Salesforce Connect, Einstein Analytics,
Platform Events
— Jitterbit #1 Data Loader on AppExchange
Customer since 2012
The API Transformation CompanyTM
Founded in 2003
Investors: Salesforce.com, KKR, Autodesk,
Primera Capital
Jitterbit Profile

3. Powering the Connected Campus in Higher Education

4. Taylor University
Christian discipleship residential liberal arts institution located in Upland, IN with 1,900
undergraduate students studying over 60 majors.
• 90% tuition-driven revenue
• 97% in Grad School or Employed within 6 months of graduation
• Popular majors: Business, Education, Kinesiology, Engineering, Computer Science
• Banner is the University’s SIS

5. Salesforce & Jitterbit History
Admissions started using Salesforce in 2011 originally for our campus visit program and to track
emails and phone calls with prospective students.
A few years later we pulled our Inquiry pool out of Banner but kept our admissions application
process in Banner.
In 2013, we started using Jitterbit to integrate our systems and to automate our workflows.
In 2016 we removed our entire process from Banner. Records are created in Banner at the time
of matriculation so the general student record is created
In 2017 we moved to a brand new HEDA Salesforce org along with a jump to Pardot as our
marketing tool.

6. What we were looking to accomplish
1) How can we streamline our Admissions/Enrollment process?
2) How can we manage a complex multi-year admissions process and expand our 10k prospect
base?
3) How can we optimize our campus visits?
4) How can we use Salesforce, Pardot and other tools to deliver compelling communications?
5) How do we integrate enrollment and non-enrollment data from so many systems?
6) How do we ensure all information is accurate and how do we do this quickly?

7. How did we decide to move to HEDA?
Direction that the Higher Ed community was moving.
• Salesforce future focus
• AppExchange/Open Source
We wanted to prepare our Salesforce org to be ready for the rest of the university to join us.
Apps on the AppExchange did not play well with Person Accounts
• Extra set up
• Some did not work
• Updating some apps was challenging
Merging Community Accounts
• Had to deactivate community accounts before merging Person Account records

8. Building our HEDA org
Gave us a chance to evaluate what was working and where we could make improvements
Moved to keeping digital files instead of paper files for applicants
Built objects to control processes where other staff could update them
• Territories
• ACT/SAT major crosswalk to Taylor majors
Use HEDA objects where we could
Built objects to map codes and descriptions
• Map to codes used in Banner
• Map recruiting majors to college/department/major/concentration in Banner

9. Planning the Migration to HEDA
Decided what records needed to be moved and what could be archived
Decided what order records needed to be loaded into the HEDA org and map the fields from
the old org to the new org
• Some changed objects
• New field names (implemented naming conventions)
Built formula fields in the old org that converted values to new values
• No need to massage data after it was extracted
Created an “Old Org ID” field on all objects so matching child objects could be done easily
• Started loading records in BEFORE we made the jump and just updated records that were changed.

10. Tools used to Extract/Load files for Migration
Salesforce Reports
• Straight forward files
WebFocus/Data Replicate tables
• Used when I needed to manipulate the fields
before loading
Jitterbit
• Easy to match up records
Configero Data Loader
• No API calls
• Control batch sixe

11. User Testing and Preparation before Migration
After HEDA was built, we had our application processing staff, admissions counselors and visit
staff test the HEDA org
• Modifications were made based on their suggestions/issues
Scheduled several weeks to plan and build the migration files
Went through a practice runs with a limited number of records in a sandbox to make sure the
migration worked as planned
Prepared HEDA org for Records from Old Org
• Turned off Trigger
• Turned off Process Builders
• Turned off Workflows

12. Lessons Learned
HEDA is a blank slate with an ever evolving and improving future
• At the time of our migration there wasn’t anything for Admissions/Recruiting
• The Higher Ed Community is a vital asset.
• Looking into EASY application and Student Interactions
Should have used Jitterbit BULK insert/upsert to load Migration files
• Starting with Pardot at the same time, I was unsure how many API calls I would be using
• BULK processes would have minimized the API calls used
• Would have sped the process up tremendously

13. How Salesforce/Jitterbit has transformed our organization
Streamlined our
Admissions/Enrollment
processes
• Centralized data & automation
• 1:1 communication
Balloon prospect pool from an
annual 10K to 60K
• Manage a more complex and
multi-year admissions cycle
• These prospects now account
for 20-25% of each enrolling
class
Systematic streamlining of
campus visits from creation to
fulfillment
• 2,000+ each year
• Most expensive part of budget
Leverage Salesforce and
Pardot to deliver each year:
• 50+K text messages
• 2 million emails
• 250K print pieces
Implementation across non-
enrollment areas - student
services, athletics, academics
• More complete sales cycle
• Leverage enrollment data
Jitterbit has allowed us on a
daily basis to:
• Correct data
• Integrate with Banner,
PowerFaids and further with
Pardot
• Fill in where PB, Workflows and
Flows fell short
360 Degree View

14. Q&A
Mike Muhlfelder, VP of Sales, Jitterbit
Sue Ours, Enrollment Management Systems Administrator,
Taylor University