Skip to main content

Analytics cookies

We’d like to use Google Analytics cookies to learn how this site is used and improve it. Nothing is set unless you accept, and there are no advertising cookies. Change your mind anytime under “Cookie settings” in the footer. Privacy policy

Modernization

Legacy applications moved onto modern platforms in steps, without starting from zero and without stopping the work that depends on them. We modernize what should change and connect what should stay.

12
process centers where PepsiCo R&D associates browse and book pilot-plant equipment
9
engagements with Honda Research Institute

Schematic — client UI under NDA

  • Legacy systems
  • APIs and integration
  • Modern platform

Trusted by

  • PepsiCo
  • Honda Research Institute
  • State of Ohio
  • Stanford University

Most organizations cannot replace everything at once. We modernize in steps: move what needs to move, connect what should stay, and keep the whole environment running while it changes.

For PepsiCo R&D we built the Process Gallery (2016–2019), where associates browse and book pilot-plant equipment across 12 process centers. For Honda Research Institute a research prototype became a production platform in 2016 and moved to Honda’s infrastructure in Japan in 2018–2019, so teams in the US and Japan work from the same data. For Stanford University we took AXESS from a 2021 redesign to a 2022 implementation on Liferay DXP, with an accessible theme.

Modern platforms, without starting from zero.

  • An honest assessment

    What you have, what it costs to keep, and what to modernize first.

  • APIs and integration

    Modern front ends and services connected to the systems that should stay.

  • Data migration

    Data moved and cleaned in phases, with the old system running until the new one is proven.

  • Platform upgrades

    Version upgrades of custom modules and themes, as for CMAP’s move to Liferay DXP 7.2.

  • Accessibility in the rebuild

    A rebuild is the cheapest moment to fix accessibility; we build it in, as in Stanford’s accessible theme.

  • Teams ready for the new platform

    Training and documentation so your people run what we modernize.

From legacy to modern, one step at a time.

  1. Evaluate

    Applications, dependencies and users, and the order that avoids disruption.

  2. Prototype

    The target experience and architecture, proven on one slice before the rest.

  3. Build

    Modernization in agile increments, with legacy systems running alongside.

  4. Adopt

    Training, cutover and support, so the new platform is the one people use.

Platforms we build on

  • IBM
  • Liferay DXP
  • HCL Digital Experience

Bring us the hard problem.

Book 30 minutes with the senior people who would do the work.

Or write to info@base22.com