DVL Group connected HubSpot deals to SharePoint and its ERP, then changed ERPs

The Customer

DVL Group is a company running HubSpot alongside its ERP. In 2021 their sales team worked deals in HubSpot, their project teams worked in SharePoint project sites, and their ERP was Microsoft Dynamics SL. DVL came to Lynton in June 2021 to expand the integration between those systems. Three years and one ERP later, the integration was still running in 2024.

The Challenge

A deal in the CRM becomes a project, and that project has to exist in SharePoint for the delivery team and in the ERP. The integration’s job was to take a deal entered once and carry it into the other two systems, along with the project files and the quarterly SharePoint sites that go with it.

Then in 2023 DVL replaced Dynamics SL with Acumatica, working with an Acumatica partner. The SL side of the integration now pointed at a system that was going away.

The Solution

In 2021 we built three sync maps: CRM deals to SharePoint project sites, SharePoint quarter sites created automatically, and SharePoint to Dynamics SL through SQL. DVL approved the sync logic and field mappings before development began, tested the build over two rounds of acceptance testing, and confirmed it was working to specification about seven weeks after kickoff. On August 2, 2021 we ran the historical sync: every deal in the CRM to SharePoint, and everything in Dynamics SL with a deal ID back to SharePoint. We then handed the integration to our support team with documentation and a walkthrough of the build.

Later that year, after a discovery engagement that produced an integration strategy blueprint and an updated roadmap with development estimates, we added a second piece: a migration of CRM attachments to SharePoint, with its own acceptance testing and a second historical sync in December 2021.

When DVL moved to Acumatica, we replaced the SL pieces. Two new maps were built against Acumatica’s REST API: Acumatica customers to CRM companies, and CRM deals to Acumatica projects. Each Acumatica project carries the deal ID as an attribute, so a deal that syncs again updates the same project. We worked with DVL’s Acumatica partner on the API endpoints, and DVL tested in three rounds: customers, then projects, then everything together before launch. We switched off the Dynamics SL pieces in January 2024, updated the documentation, launched in March 2024 and handed the integration back to our support team.

What They Got

DVL’s sales team enters a deal once in their CRM. The project appears in SharePoint for delivery and in Acumatica, and each Acumatica customer is mirrored as a company in the CRM. Through a change of ERP, only the Dynamics SL pieces of the integration were switched off.

Wrapping Up

Our standard on an integration is to agree the sync logic and field mappings in writing before development, to have the client test every map before the historical sync, and to build each connection so one piece can be replaced when a system changes. Lynton now builds AI-native websites on open infrastructure; see our current work at /case-studies.