PerkinElmer Migrates 1,600 Pages to Drupal on Acquia DXP in Three Months

Staff Reporter

PerkinElmer’s attempt to modernize its B2B digital presence led to a rapid but ambitious three-month website relaunch in partnership with Bounteous. Tasked with replacing a legacy Tridion system, the team migrated 1,600 pages to Drupal using the Acquia Digital Experience Platform, while integrating Acquia DAM, HubSpot, and API-based search. The relaunch marks a pivotal step in aligning digital infrastructure with a broader business shift toward customer-centric service delivery.

Despite the tight timeline, the engagement delivered tangible results: a more flexible architecture, faster content authoring, and over an 80-point jump in SEO scores. Bounteous deployed several proprietary accelerators—ranging from PDF conversion to AI-assisted content authoring—to expedite implementation and streamline workflows. These tools supported PerkinElmer’s goals but raise questions about long-term platform dependency and the portability of such accelerators.

While the case study is framed as a technical success, its business impact remains partially anecdotal. The initiative demonstrates how Drupal, paired with Acquia, can facilitate agile enterprise transformations—but also underscores how tightly such outcomes hinge on vendor-specific tooling and support.

Reference: Building a Foundation for B2B Transformation with Web Experience, Bounteous

Drupal

Bounteous

Disclosure: This content is produced with the assistance of AI.

Disclaimer: The opinions expressed in this story do not necessarily represent that of TheDropTimes. We regularly share third-party blog posts that feature Drupal in good faith. TDT recommends Reader's discretion while consuming such content, as the veracity/authenticity of the story depends on the blogger and their motives.

Note: The vision of this web portal is to help promote news and stories around the Drupal community and promote and celebrate the people and organizations in the community. We strive to create and distribute our content based on these content policy. If you see any omission/variation on this please reach out to us at #thedroptimes channel on Drupal Slack and we will try to address the issue as best we can.