What can I expect?
This phase is dedicated to building the architecture of the integration, training the project team on using the Vertify product, and then advancing towards testing.
Questions to consider can include: what data points do you want to move, how many records does that represent, and how do you want records to be merged?
Your integration team will collectively participate in this discussion designed to get the group thinking and clarify the type and structure of your integration. This is potentially the most important phase of our process, and the decisions made here will impact the rest of the integration.
Vertify Product Training:
- Your lead specialist will share with the team your Vertify tenant site and your system credentials.
Object and Field Mapping:
- During this time, your lead specialist will also be working on setting up initial best practice mappings (if available) for your integration which you can then customize to your liking.
- You, the customer, will decide which fields need to be mapped between the systems using the best practice mappings outlined as a baseline.
- At this time, you'll also start meeting for working sessions during which the lead specialist can provide assistance and help answer questions about the integration to help you determine your requirements.
Integration Design Document:
- Partner with the lead specialist to create a document of the integration including the above field mappings.
- This is also a good time to start considering what data you need and for which audiences, as well as how records will be matched between systems.
- You'll start to identify or create a few test records in the CRM (1-2 is fine at first) for each object being used (i.e., Contact, Company, Opportunity).
- While customizing mappings, it's helpful to see the data created and updated with the assistance of test records that can be moved without issue.
- Once mappings have been refined and movements are ready for heavier data testing, you'll transition to the next phase.
Best Practice Notes:
- If your teams do not need some data, consider not moving it. Moving and syncing unneeded data simply adds complexity and adds additional work to your teams to keep clean data and manage errors.
- It is very frustrating for customers to have important records stop syncing due to a non-important field having bad data and blocking the sync process. If it isn’t vital, don’t move it. You can add the field later if it becomes vital.