Confidential & Privileged DocumentConfidential & Privileged Document
Agenda
• Who should be involved?
• What does it take to transition?
• What can clients do to prepare?
Confidential & Privileged DocumentConfidential & Privileged Document
Pre-Build Phase
• Client project team works with the Baker Hill team to:
– Initiate the project/transition
– Client to clean up current production database (Advisor/BHOS)
Confidential & Privileged DocumentConfidential & Privileged Document
Build/Transition Phase
• Baker Hill project team conducts first test transition:
– Client will receive training
– Baker Hill team makes a copy of current production database(s) and
transitions it to NextGen
Build/Transition Phase
Confidential & Privileged DocumentConfidential & Privileged Document
User Acceptance Testing
• Baker Hill and client teams work together to test the
transitioned database(s)
– Client is updating processes based on new NextGen database
– Client is validating configurations and data
– Client is receiving more training, if applicable
– Client is still using Advisor/BHOS database for daily production use
User Acceptance
Testing
Build/Transition
Phase
Confidential & Privileged DocumentConfidential & Privileged Document
Production Roll-out Phase
• Final transition is completed in a production environment:
– Client begins to use NextGen database as production environment
– Client is receiving more training, if applicable
Production
Roll-out
User
Acceptance
Testing
Build/Transition
Confidential & Privileged DocumentConfidential & Privileged Document
Close-out Phase
• Confirm transition is complete and issues start going to
support.
– Assign a Technical Account Manager to client post production to
ensure client adoption for a period of 3-4 months
Production
Roll-out
Close-out
User
Acceptance
Testing
Build/Transition