Company ABC made the decision to leave FreshSales at the beginning of 2023 as it did not need the company’s growing CRM, Marketing and Sales Needs . Company ABC contracted HubSnacks for help in moving their FreshSales data to HubSpot. This migration encompassed preserving the existing historical data architecture established in FreshSales, alongside upholding data quality and integrity. This entailed migrating all historical activity data, including emails, tasks, notes, meeting recordings, and call data, to ensure a seamless transition.
The following data migration project criteria were crucial to the success of the overall data migration project. By using a custom-built migration script specifically designed for Company ABC’s needs, the HubSnacks team was able to accomplish the following:
- Migrated all historical lead records with associated properties and activity records to HubSpot.
- Migrated all historical lead records associations such as account and opportunity data to HubSpot.
- Migrated all historical contact records with associated properties and activity records to HubSpot.
- Migrated all historical contact records associations such as account and opportunity data to HubSpot.
- Migrated all historical opportunity records with associated properties and activity records to HubSpot.
- Migrated all historical opportunity record associations such as account and lead data to HubSpot.
Do you want a solution like this?
-
To ensure that the data migration did not interfere with the client's live HubSpot account until everything was set up to the customer's preference, the data migration script was first deployed in aHubSpot Developer account. After the data migration solution was signed off by the customer, the HubSnacks team proceeded to build out the data migration solution in the customer's live HubSpot account.
The hosted data migration solution was built into the HubSnacks integration platform and allowed for HubSpot Private App APIs to be used in a way that maximized usage of all software data involved. The HubSnacks data migration platform also allowed for a seamless way to generate reliable data sync between FreshSales and HubSpot for the Company ABC’s team.
The Process
When a customer, such as Company ABC, approaches HubSnacks, the following tested and perfected methodology is followed to ensure that each customer gets the best data migration solution they desire.
Once a data migration request came in, the HubSnacks integration team evaluated what was required, how best the data migration could be done, and if the required data architecture was possible within a customer's HubSpot subscription. By doing so, the HubSnacks team ensured that all possible data points that should have been migrated were migrated to HubSpot.
After thoroughly researching every possible data migration avenue, the HubSnacks integration team will present a data migration solution to a customer with a detailed overview of the data flow.
Succeeding an agreed-upon quote, the HubSnacks Integration team will set up a meeting with the Data Migration customer to start the integration project with a kickoff meeting.
The purpose of this call will be for the HubSnacks Integration team to understand
the current set-up of the customer's software that they wish to migrate from..
During the integration kick-off call, the HubSnack team will require a live
demo/walkthrough of the current software set-up. This allows the HubSnacks team to create an accurate Scope of Work (SOW).
The HubSnacks team conducts a Full Tech Stack Audit after the initial call. During this audit, the team looks into prior use cases to speed up the data migration process and installation, assesses what can be handled by Operation Hub, and contacts our elite support team in HubSpot to run a checklist of best practices against this client's use cases.
Once the best data migration path is confirmed, the HubSnacks Integration team will create a Scope of Work (SOW) document outlining the work to be completed. The Scope of Work (SOW) will include a detailed summary of the customers' data migration requirements.
This Scope of Work will then be sent to the customer and discussed and optimised during Call 2. Once the final Scope of Work is defined, agreed upon, and signed by both parties, the HubSnacks Integration team will start with the data migration.
A third call is then needed for the HubSnacks team to present the proposed data mappings used during the data migration. This will ensure that the data that will be transferred will be done in an efficient way so that the customer can easily understand the new migration/systems set-up. The third call will also be utilised to discuss custom objects and properties required by the HubSnacks team for successful data migration.
The 4th and final call that will then be scheduled with the customer will happen as soon as the required data migration has been set up and ready to be handed over. During this session, the HubSnacks team will explain to the customer how the new data architecture works and do a live demonstration of the data now in HubSpot.