When your IP docketing system or IPMS gets acquired: what actually changes, what to ask your vendor, and why you shouldn't panic into a migration.
Platforms get acquired. Roadmaps shift. Here's how to protect your operations without panicking into a migration.
A docketing manager opens her inbox on a Tuesday and there's a press release waiting. The docketing system her firm has run for a decade just got acquired. New parent company, new logo on the login page eventually, and a lot of reassuring language about continuity and exciting roadmaps.
Her first question isn't strategic. It's practical. Does anything I do today change? And right behind it: is this the start of a migration I didn't ask for?
If you've run an IP practice for any length of time, you've had this Tuesday. IPMS consolidation isn't new. The market has been consolidating for years. Platforms get bought. Roadmaps shift. Migration plans get announced, delayed, revised, and announced again. The most recent one is Anaqua's acquisition of Patrix and its Patricia platform in April 2026, but it won't be the last. Plenty of firms running a mature docketing system have already been through it at least once.
So the useful question isn't "what do we do about this acquisition." It's "how do we run operations so the next one doesn't rattle us." Here's how to think about it.
Should You Panic When Your IP Software Vendor Gets Acquired?
No. And the firms that do the worst after an acquisition are usually the ones that overreact.
The day after the announcement, almost nothing about your actual work has changed. Your data is where it was. Your dockets are intact. Your team logs in to the same system and does the same job. Acquisitions are slow. Whatever the new owner plans, it plays out over quarters and years, not over the weekend.
The mistake isn't staying calm. It's either of the two overreactions: panic-migrating to a different system before you have to, or assuming nothing will ever change and getting caught flat-footed in two years. The right posture is in between. Calm, and paying attention.
What Actually Changes After an IPMS Acquisition?
In the short term, very little. In the long term, four things are worth watching.
The roadmap. The features you were promised may get reprioritized to fit the new owner's platform strategy. The thing you were waiting for might ship later, or differently, or get folded into a product you'd have to buy separately.
Support and the people. The team you knew may change. Response times can drift while the org integrates. The person who understood your configuration might not be there next year.
Pricing and packaging. Renewals are where acquisition economics usually show up. Watch the next contract cycle for repackaging, bundling, or price changes tied to the new owner's model.
The migration question. Sooner or later, many acquirers want their customers on a flagship platform. It may never come for you. But "integrate and elevate" can quietly become "migrate when convenient for us," and you want to see that coming.
None of these is a reason to run. They're reasons to ask sharper questions.
What Should You Ask Your Vendor After the Acquisition?
Get the answers in writing, not in a webinar. Five questions:
- Is our platform's roadmap continuing as-is, and for how long is that committed?
- Does our support team and our point of contact stay the same?
- What changes at our next renewal, on price and on packaging?
- If a migration to another platform is ever expected, what's the timeline and who bears the cost?
- Who owns our data, where does it live, and how do we get a full export if we ever leave?
The quality of the answers tells you more than the acquisition itself. A vendor that answers plainly is one thing. A vendor that keeps returning to "exciting synergies" without committing to specifics is telling you something too.
Should You Migrate to a New Docketing System?
Usually not, and almost never reflexively.
Ripping out a docketing system is one of the most disruptive things an IP practice can do to itself. You spent years configuring it, building workflows around it, and training a team on it. A migration puts all of that at risk, ties up your team for months, and introduces the exact thing your docket can't afford: a window where a date can slip through the gap between the old system and the new one. Doing that because of an acquisition, before the new owner has even shown their hand, trades a manageable uncertainty for a real and immediate risk.
There are good reasons to migrate someday. An acquisition, on its own, usually isn't one of them. Let the new owner earn the migration, or force it. Don't volunteer for it out of anxiety.
How Do You Make Your Operations Acquisition-Proof?
You can't control who buys your vendor. You can control how much of your operation is hostage to that vendor's roadmap.
Here's the move that does the most to de-risk the next acquisition: stop running your operations inside the docketing system, and start running them on a layer that sits above it. Your docketing system should do what it's great at, which is holding your dates and your case data. The operational work around it, the dashboards, the client reporting, the forms, the workflow that moves a matter from the inbox to filed, doesn't have to live inside that one vendor's product. When it lives in a layer on top, the layer doesn't care who owns the IPMS underneath.
That's what PracticeLink does. It runs your operations on top of the docketing system you already have, and it connects to FoundationIP, CPi, Inprotech, Patricia, and the others. If your IPMS continues as-is, PracticeLink continues with it. If it changes, or if you do eventually decide to move, you reconnect the layer to the new system instead of rebuilding your operation from scratch. The dashboards, reporting, client portals, and workflows you built stay in place. What changes underneath them is the connection, not the operation. The operations layer is the part that stays constant while the vendor underneath gets acquired, rebranded, repriced, or replaced.
And adding it isn't a data migration. There's setup, but you're not moving your dockets or replacing your system. PracticeLink reads from the systems you already run, so you're not trading one rip-and-replace for another. Five of the top 10 US patent filing firms run it this way, alongside their existing docketing systems rather than instead of them.
That's a different kind of insurance than picking the "right" vendor. There is no acquisition-proof vendor. There's only an operation built so the next acquisition is someone else's headache, not yours.
Where to Start
You don't need to do anything dramatic this week. Pull your current contract and find the data-export and termination terms. Write down the five questions above and send them to your account rep. And ask one bigger question internally: if we had to change docketing systems in two years, how much of our operation would we have to rebuild?
If the answer is "most of it," that's not an acquisition problem. That's an architecture problem, and it's the one worth fixing before the next ownership change forces your hand.
If you're running Patricia specifically, we wrote about what the Anaqua acquisition means for your operations here: How PracticeLink Works with Patricia. For the broader picture on running operations as a layer above your existing tools, see How PracticeLink Connects Your Existing IP Tools.
Frequently Asked Questions
What should you do when your docketing system gets acquired?
Stay calm and pay attention. In the short term almost nothing about your daily work changes, so don't panic-migrate. Use the time to get answers in writing on four things: whether your roadmap continues, whether your support team and contact stay the same, what changes at renewal, and whether a migration is ever expected and who pays for it. Also confirm your data-ownership and export terms. The acquisition itself is rarely a reason to switch systems. It's a reason to ask sharper questions and to make sure your operations don't depend on any single vendor's roadmap.
Should you switch IP management systems after an acquisition?
Usually not, and never reflexively. Migrating a docketing system is one of the most disruptive things an IP practice can do, and doing it out of anxiety, before the new owner has shown their plans, trades a manageable uncertainty for an immediate risk: a window where a date can slip through the gap between systems. There are good reasons to migrate someday, but an acquisition on its own usually isn't one. Let the new owner earn or force the migration rather than volunteering for it.
How do you protect your IP operations from vendor consolidation?
Run your operations on a layer that sits above the docketing system rather than inside it. Your IPMS holds your dates and case data. The operational work around it, such as dashboards, client reporting, forms, and workflow, can live in a layer on top that connects to whichever IPMS you run. When operations live in that layer, a vendor acquisition, rebrand, or even a future migration doesn't force you to rebuild them. There's no acquisition-proof vendor, but there is an acquisition-resilient way to build your operation.
What does the Anaqua acquisition of Patrix mean for Patricia firms?
For most Patricia firms, the day-to-day hasn't changed. Anaqua has publicly said it will continue supporting the Patricia platform and its roadmap. The longer-term question is the same one any firm should ask after a vendor acquisition: how to invest in operations without tying everything to one IPMS roadmap. Running an operations layer on top of Patricia keeps your dashboards, reporting, and workflow in place whether Patricia continues as it is, evolves, or your firm later moves to another system.