...
Sandbox time! If you are reading this document, it means you have probably already spoken to a Validic team member about doing the migration. You might also already have access to a Sandbox Org in V2. If you don’t, that will be set up soon for you.
Intake Form. In order to make sure Validic understands how you currently use V1, we need you to complete this form: https://docs.google.com/forms/d/e/1FAIpQLSe2nr0hTAWctk-lF25HLUJExdtomPIJtffTfkvK-3vitbKB5A/viewform This helps us determine if you are a good fit for migration.
Testing, testing, development, more testing. Now that you have your sandbox, you should be focusing the majority of your effort on creating test users, connecting the test users to sources through the marketplace, generating data, and working with the Streaming API. Throughout this process, do not hesitate to reach out in your support case with any and all questions. This is very important because we cannot move forward with the migration until you are 100% ready to use the V2 Streaming API.
Mirroring V1 data. Testing in a sandbox is great for development, but it doesn’t really accurately show you what your actual user data will look like once migrated to V2. This is where “data mirroring” comes in. At least 30 days before your desired migration, Validic will create a duplicate of your V1 production org in V2. It will have the exact same Org ID, but a different Access Token. At the same time, we will start “mirroring” your incoming V1 data into this V2 org. Your V1 org is not affected in any way by this.The purpose for the mirroring is to allow you to see what a full load of customer data will look like in the streaming API to make sure you are prepared for the volume you will see after migrationImportant: You may use this data to load test, however, not all metrics or sources are covered in the mirrored stream. That said, you can use it to backfill data as long as you have noted the format of the data in the mirrored stream compared to what you see in your sandbox.
It’s a date! Once you have fully completed the above, we will schedule some time to talk through what you have completed and then confirm a date for the actual migration. If you are not yet ready to 100% use the streaming API for your production data, you are not ready to migrate and therefore a date may not be set until you are. Migrations are done on Tuesdays or Wednesdays during US business hours to ensure all resources are available.
...
Inform your users that your Marketplace will be down for potentially several hours on the day of migration. This is the extent of any “outage” that they might experience.
Approximately 1 week before migration, you should complete user “housekeeping” by deleting users from your V1 org that you are confident are old/inactive/etc. No point migrating users that are no longer active
1-2 days before the migration date, you should stop all user management processes. For organizations with large numbers of users, Validic will start to replicate the user IDs over to V2 prior to migration day (with no effect on V1). We rely heavily on having accurate user counts during migration so if your system is adding or removing users during this time it can throw off our counts and result in a longer time to complete the migration.
Either the night before, or early on the day of migration, you should disable your V1 marketplace access for users and instead display your maintenance page. This will need to remain in place until the migration is complete later in the day on migration day.
On migration day, all you have to do is wait for Validic to let you know that you can turn the marketplace back on, only this time it will be the V2 marketplace
Process Summary
Day 1: CSE opens a support case and you receive the intake form to fill out A Validic team member will open support case that will be the central point of communication throughout the migration process. The first meeting is scheduled through the support case. All relevant client contacts are added to the support ticket for visibility.
...