The functionality of your source and target CRMs will most likely differ. To eliminate discrepancies and data loss, we’ve outlined several possible scenarios along with our solutions for these scenarios. Check to see how Trujay handles each scenario below.
Scenario 1: An object relation is required in your target CRM, but does not exist in your source CRM.
Say you have contacts that exist without relations to companies in your source CRM, but in your target CRM, contacts can only exist with relation to a company.
Solution: Trujay will create a fake company and automatically assign this company as a relation to all contacts without a company relation during the migration process.
Scenario 2: An obligatory relation exists within your target CRM between an object you opted to migrate, and an object you omitted from the migration process.
Assume you have selected the “contacts” object for migration and opted out of migrating the “companies” object, however, your target CRM requires a contact-company relation.
Solution: Trujay will create a fake company and automatically assign this company as a relation to all contacts missing a company relation during the migration process.
Scenario 3: A record in your target CRM requires a relation to an object that does not exist in your source CRM.
An example may be that an opportunity-line item relation is required in your target CRM, and a line item object doesn’t exist in your source CRM.
Solution: Trujay will create a fake line item within your target CRM and automatically create a relation between this line item and all your migrated opportunity records during the migration process.
In conclusion, Trujay utilizes fake record creation for the purpose of ensuring required relations between objects are fulfilled, all your data is kept in place, and data loss is avoided during your migration process.