If you're considering migrating your CRM system to Salesforce, there are a few essential factors to consider in order not to affect MadKudu and your scoring pipeline.

This article is for teams that will handle the migration and for teams that operate MadKudu, to ensure that your scoring pipeline is not disrupted for your Sales teams and they keep having a seamless experience.

One of the most critical elements is ensuring that migrated data is identified from new data in Salesforce. Follow these guidelines to ensure a smooth and successful migration process.

Before the migration: prepare Salesforce

Install the MadKudu Salesforce package

You currently receive MadKudu scores in your HubSpot. When migrating to Salesforce, you'll need to receive MadKudu scores in dedicated Salesforce fields. Install the MadKudu Salesforce package and you'll be good to go! >> MadKudu Salesforce Package

Preserve Creation Dates

When you import your HubSpot records into Salesforce, they will be marked with a new creation date.

It's useful to freeze original creation dates from company, contacts, and deals in a custom Salesforce field for all objects: account, lead and/or contact, and opportunity.

It will allow you to keep track of when these records were actually created.

Preserve Closed Dates for Deals

In the same fashion as creation dates, it's essential to capture closed dates of deals accurately.

If you cannot save this original date in the closeddate field, save it in a custom field.

Preserve Event Timestamps for Forms

If you plan to also migrate HubSpot forms to another system, it's essential to preserve event timestamps. The event timestamp tracks when a form was submitted.

This information is key for your behavioral segmentation.

Create a "is migrated" checkbox

A boolean field identifying which record has been migrated from your previous CRM from which record has been natively created in Salesforce always comes in handy, for various tools, processes, and workflows. 

When you stop using HubSpot: prepare MadKudu

Connect Salesforce to MadKudu

First things first >> Salesforce

Replace HubSpot attributes

Before you stop creating new records in HubSpot, check if you are using any demographic or firmographic enrichment from HubSpot in MadKudu

>> Attribute mapping

If you do, pull and map the corresponding Salesforce fields in MadKudu.

>> I want to use a field from my CRM in the Data Studio. How do I do this?

Then, replace those attributes in your customer fit segmentations. Our support team can assist you! Submit a ticket.

Replace HubSpot forms

If you do not keep using HubSpot as your Marketing Automation Platform, where will this information end up in your new stack?

>> How to create or edit the Event mapping?

If you plan to replace them with Salesforce Campaigns, learn more here >> Event mapping: Salesforce Campaigns

Push MadKudu intelligence to Salesforce

Once your Salesforce instance is set up and is ready to be used by your Sales teams, connect it to MadKudu >> Salesforce

Then, head to your push configuration panel, and set up the push of MadKudu intelligence to Salesforce >> How to push MadKudu Intelligence to your integrations?

When can I create new segmentations using Salesforce?

You will need to have been using Salesforce for several months.

Your current segmentation, based on Hubspot data, will keep running (even after you disconnect HubSpot). It is sending scores to Salesforce. But you cannot train a new model based on Salesforce data for 6 months to 1 year. This is because right after migration, recent and old records (such as leads, contacts, opportunities...) are all mixed, having the same creation date. All of the system creation and closed dates (the ones created automatically by Salesforce) of your migrated records are not accurate after migration.

Most MadKudu reports and metrics rely on system creation dates, not the original dates that you preserved in custom fields.

So you will need to accumulate 6 months to 1 year of new data with accurate dates in Salesforce. The more 'clean' data, the better.

For example, your MadKudu lead & account segmentation is based on deals you previously closed or lost, so we want to avoid mixing 2 years old deals with very recent ones. It's also based on the type of contact that helped you close the deals, so contact creation dates are key, too.

Closed dates are also used in multiple forecasting and reporting within MadKudu, and in particular, to track your revenue over time for each of your account & lead segments.

What do I do in the meantime?

You already have performing segmentations based on your HubSpot data, sending scores to Salesforce. Keep these segmentations running with no modification while you accumulate enough new data in your brand-new Salesforce instance.

After a few months to a year, you'll be able to update your segmentations based on Salesforce data. The 'is migrated' checkbox will be very helpful at this time to differentiate migrated data from new data!

By following these guidelines, you can ensure that your migration from HubSpot to Salesforce will be smooth within MadKudu and won't cause any disruptions in your scoring.

If you have any questions or need additional support, reach out to our customer support team for assistance!