Skip to content
Case study Application maintenance

How Provis keeps LFT (Law Firm Tools) running, and is cleaning up its architecture before a move to PHP 8.

LFT is an existing legal application on a legacy PHP and Yii stack, and older technology is hard to maintain. Provis maintains it, ships updates and fixes, and is cleaning up its architecture. A move to PHP 8 is planned for once that is stable. It has not happened yet.

  • Maintenance
  • Architecture clean-up
  • PHP 8 planned
An illustrative desktop screen of a legal practice application: a list of open matters, deadlines, time this week and recent documents
An illustrative phone screen of a legal practice application: a list of four open matters
Client: LFT (Law Firm Tools)Legal practice tools, United States
Where the work stands

Kept running now, tidied next, upgraded later.

Kept running
Ongoing
Updates and fixes keep the application working for its users
Tidier code
Being done
Cleaning up how the application is put together makes it easier and safer to change
PHP 8
Planned, not done
A newer PHP version comes after the clean-up, so the application stays supported

At a glance

  1. Problem

    The application runs on a legacy PHP and Yii stack, and maintaining older technology is challenging.

  2. Solution

    Provis maintains it, ships updates and fixes, and is cleaning up the architecture so a move to PHP 8 can follow.

  3. Status

    Maintenance and the architecture clean-up are ongoing. The PHP 8 move is planned, not done.

Client
LFT (Law Firm Tools)
Industry
Legal technology: practice tools for law firms
Market
United States
Services
Application maintenance, architecture clean-up, planned PHP upgrade
Stack
A legacy PHP and Yii stack, with a move to PHP 8 planned
Status
Ongoing: maintenance and architecture clean-up. Planned: PHP 8
The situation

A working application on a stack that is getting harder to keep.

LFT has an existing legal application, and Provis maintains and improves it. The application runs on a legacy PHP and Yii stack.

Maintaining older technology is challenging. Moving to a current PHP version is the goal, but the architecture has to be in good shape first, and the application has to keep working throughout.

How an older application usually ages

  1. Built and in useon the tools of its day
  2. Tools move onthe framework and PHP version fall behind
  3. Changes get hardereach fix touches tangled code
  4. Support runs outold versions stop getting security fixes

A typical flow for applications like this, not a record of this client.

The problems, and what fixed each

Keep it running now, and get it ready to move.

The two problems Provis is working on, and where each stands.

  1. An older stack that is hard to maintain

    The application runs on a legacy PHP and Yii stack, and maintaining older technology is challenging.

    What Provis doesOngoing maintenance, updates and fixes

    Provis maintains the existing application, implements updates and corrections, and keeps it working.

  2. An architecture that is not ready for a newer PHP

    A move to a current PHP version goes better once the architecture is clean and stable. The application also has to keep all its functionality.

    What Provis is doingAn architecture clean-up, then a planned move to PHP 8

    Provis is reviewing the architecture and cleaning it up. The move to PHP 8 is planned for after it is stable. That move has not been done yet.

How the work ran

The plan: clean up first, then move to PHP 8.

  1. Review the architecture (ongoing)Look at how the existing application is put together
  2. Refactor and clean up (ongoing)Tidy the code and the structure of the application
  3. Reach a stable state (planned)The architecture is sound enough to move
  4. Upgrade to PHP 8 (planned)Move to a current PHP version, with functionality kept working
  • Today: Provis maintains the application and ships updates and fixes.

  • Under way: reviewing the architecture and cleaning it up.

  • Planned: a move to PHP 8, once the architecture is stable. It is not done yet.

How the move is planned:

Clean up first, then upgrade.

A move to PHP 8 is planned for after the architecture is sufficiently improved. It is a future step, not a finished one.

Existing functionality is to keep working through the transition.

How Provis builds and runs web applications
The application

What a legal practice application looks like.

Illustrative screens, designed in Law Firm Tools' style; the real application is private. The matters, people and documents shown are made up. Select one to enlarge it.

  • An illustrative list of four open matters, each with a type, a lawyer and a status

    MattersEvery case in one list

  • An illustrative documents tab for one matter, with four sample documents and their versions

    DocumentsKept with their matter

  • An illustrative deadlines screen split into this week and next week

    DeadlinesWhat is due, and when

  • An illustrative time entries screen with four entries and the total hours for the week

    Time entriesHours by matter

  • An illustrative settings screen with account details and notification choices

    SettingsAccount and reminders

Where it stands

Maintained today, with PHP 8 still ahead.

The application is in use and in Provis's care. The move to PHP 8 is planned, not done.

After launch

Maintained, and being improved.

Provis maintains the application, ships updates and fixes, and is cleaning up its architecture. This is ongoing.

The move to PHP 8 is planned for after the architecture is stable. It has not been done.

Provis has delivered 200+ projects since 2012, with a team of 25+ engineers, designers, QA and project leads.

Every Provis build comes with 24/7 monitoring and support after launch.

How every Provis project runs

  • One project leadyour single point of contact
  • A written weekly update and a demoof what was built that week
  • A staging link and your repoyou see the work as it is built; the code goes straight into your repo
  • QA before launchour QA team tests every feature
  • Yours from day onecode repo, cloud account and domain in your company's name; our team joins as collaborators, and you can remove access at any time
  • Our team works in India, on ISTUTC+5:30: 1.5 hours ahead of Dubai, 4.5 ahead of London (5.5 in winter), 9.5 ahead of New York (10.5 in winter)
Start a conversation

Running an older application that needs care?

Tell us what it runs on and what you want to keep working. We will come back within two working days with an approach, a rough timeline and a rough cost range. No charge, no commitment.

Send us a message

indicates a required field

Our team in India (IST) reads every message.