Moving to a New IP Management System: A 14-Step Docket Migration Checklist
Most docket migrations don't fail at import. They fail in the weeks between two systems. Here's a 14-step sequence for extraction, register reconciliation, parallel runs and annuity handover.
Where Deadlines Actually Get Lost in a Docket Move
Picking the new platform is the easy part. The harder question: on the day you switch off the old system, how will you prove that every renewal, annuity and office-action deadline in the new one is right? An IP management system migration rarely fails because records won't import. It fails because they import cleanly with wrong data. A priority date shifts by a day during timezone conversion. A designated country drops off a Madrid registration. A "closed" flag suppresses an annuity the client still wanted paid.
This checklist runs 14 steps across five phases. It assumes a portfolio of a few thousand to a few tens of thousands of matters, moving between platforms such as Inprotech, Anaqua, IPfolio, Questel Equinox, PATTSY WAVE, Alt Legal or an in-house database. Order matters more than tooling. Reconcile before you recalculate, recalculate before you parallel-run, and leave annuity instructions alone until you trust the new dates.
| Phase | Steps | Typical duration | Exit criterion |
|---|---|---|---|
| Scope and freeze | 1–3 | 2–4 weeks | Signed data inventory and freeze calendar |
| Extraction and mapping | 4–5 | 3–6 weeks | Approved field map; test load matches record counts |
| Register reconciliation | 6–8 | 4–10 weeks | Open exceptions below agreed threshold |
| Parallel run | 9–11 | 60–90 days | 30 consecutive days with no unexplained date mismatches |
| Annuity handover and cutover | 12–14 | 2–6 weeks, overlapping | Signed cutover memo and first post-cutover audit |
Durations are indicative for a mid-sized portfolio and vary with data quality.
Steps 1–3: Inventory Every Deadline Source and Freeze the Rules
Step 1: Inventory every place a deadline lives. The old docketing database is only one of them. Deadlines also sit in partner spreadsheets, foreign associate reporting letters, annuity provider renewal lists, Outlook reminders and the paralegal's personal tracker for that one difficult client. Anything left off this list won't be reconciled.
Step 2: Name owners and set a materiality threshold. Give each jurisdiction group or client portfolio one accountable person. Define an exception up front: a date mismatch, a status mismatch or a missing family member. Set deadline tolerance at zero. Cosmetic fields like title capitalization can carry a tolerance.
Step 3: Set the cutover date and freeze rules. Avoid cutting over in a month with a big renewal cluster, or at year-end. Write down how the team handles new instructions, filings and office actions that arrive mid-project: who enters them, in which system, and who re-checks them. Without a rule, people will invent their own.
Steps 4–5: Extract Everything, Then Decide What Gets Recalculated
Step 4: Run a full extract, history included. Pull active, inactive, abandoned and lapsed matters, plus action history, document links and the audit trail. Lapsed records matter for restoration windows and conflict checks. History shows why a deadline was closed. Compare record counts by jurisdiction and status against the source system before anything loads.
Step 5: Map fields and choose carry-over or recalculation. This is the most consequential decision in a docketing migration. A deadline can be imported as a fixed date or regenerated by the new rules engine from base dates such as filing, priority, PCT international filing, grant and registration. Recalculation exposes where the old data was wrong. Carry-over preserves manually set dates, like extended response periods, that the engine can't know about. Most firms do both: recalculate statutory deadlines, carry over manual ones, and flag the carried-over dates for review.
Inventor names and addresses are personal data. If the new platform is hosted in another region, check transfer requirements under the GDPR, the UK GDPR, India's DPDP Act or your local equivalent before the first test load. Your data-protection advisor should sign this off.
Step 6: Reconcile Patent Data Against Official Registers
Step 6: Check base data and status against the source of record. The old system isn't the source of truth. The registers are. Typical sources include the European Patent Register for EP applications and validations, PATENTSCOPE for PCT national-phase data, and national registers such as USPTO Patent Center, the UKIPO, DPMAregister, CNIPA, the JPO and the Indian Patent Office.
Check four things per family: base dates, current status, the applicant or owner of record, and the list of designated or validated countries. EP matters cause the most trouble. A granted EP split into national validations, a Unitary Patent, or both will often import as one record, or as several with no link between them. Renewal fees for a Unitary Patent are paid to the EPO, while national validations are paid to each national office. Get that structure wrong and annuities go to the wrong office or aren't paid at all.
Some national offices offer bulk data or API access. Others allow only manual lookups. Budget extra time for jurisdictions where every check is manual.
Steps 7–8: Trademark Docket Reconciliation and the Exception Log
Step 7: Reconcile trademarks per designation, not per mark. Trademark records go wrong most often on international registrations. In WIPO's Madrid Monitor, one registration can have dozens of designations, each with its own status, refusal history and, in some countries, its own use requirement. Check each designation, then check national filings against EUIPO eSearch plus, the UKIPO, TMview and individual national registers. Also confirm renewal dates, outstanding declarations of use, and the end of the dependency period on Madrid registrations.
Step 8: Run a single exception log and work it to closure. Each mismatch gets a row: matter, field, old value, register value, new-system value, owner, resolution and date closed. Sort by deadline proximity, not by client. A mismatch on a renewal due in six weeks matters more than 200 title typos.
A hypothetical example: a 12,000-matter portfolio with average data quality might throw up exceptions on a few percent of records in the first pass. Most would be status and ownership drift rather than wrong dates. Don't start the parallel run until every date-related exception is closed.
Steps 9–11: Run Both Systems and Diff the Deadlines
Step 9: Diff computed deadlines matter by matter. Export the next 18–24 months of deadlines from both systems and compare them field by field. Explain every difference: a rules-engine difference, a fixed data error, or a new error. This is where IP deadline verification becomes evidence rather than opinion. Rules engines handle edge cases differently, including grace periods, surcharge windows, office closure days and multi-year annuity prepayments, which some jurisdictions allow or require.
Step 10: Dual-docket new events for 60–90 days. Every incoming office action, filing receipt and renewal notice goes into both systems, and a second person checks that the dates match. It's tedious, and it's the only reliable way to catch rules that misfire on live data.
Step 11: Test the outputs people rely on. Trigger reminder emails, escalation chains, client reports and the attorney daily docket. A correct deadline that never reaches the responsible attorney is a missed deadline. Make sure escalations go to someone who's still at the firm.
Step 12: Hand Over Annuity and Renewal Instructions Without a Gap
Step 12: Reconcile your portfolio against the annuity provider's list before changing anything. Whether you use Clarivate, CPI, Dennemeyer, Questel or another provider, their list of live cases and yours will differ. Look for cases they're paying that you've marked abandoned, and cases you think are live that they dropped. Settle each one in writing.
If you're also changing providers, set the cut-off by due date, not instruction date. Fix which provider handles anything due inside the overlap window, and confirm that powers of attorney, client payment authorities and local agent appointments move across where needed. Ask both providers for a closing and opening position statement covering the same cases.
Red flags: a provider that can't produce a case-level list in a structured file, renewal instructions held only in email, and "auto-pay unless instructed" settings nobody has reviewed since the portfolio was last pruned. Each can mean a double payment, or a lapse that needs restoration, if restoration is even available in that jurisdiction.
Steps 13–14: Cutover Sign-Off and the 30/90-Day Audit
Step 13: Get a written cutover sign-off. The memo should list record counts by jurisdiction and status, the closed exception log, the parallel-run diff results, confirmation of the annuity handover, and the date the old system goes read-only. The docketing manager, the operations lead and a responsible partner or head of IP should all sign. Keep the old system read-only, not deleted, for at least a full annuity and renewal cycle. Many firms keep it longer to meet record-retention policies.
Step 14: Audit at 30 and 90 days. Take a random sample, weighted toward high-value families and difficult jurisdictions, and recheck it against the registers. Then check every deadline that has come due since cutover for completion evidence. If the 90-day audit is clean, close the project. If not, find the cause before calling the migration finished.
Professional liability insurers in some markets ask how docketing changes were controlled. Your broker can tell you what documentation your policy expects.
What Drives Migration Cost and Which Proposals to Push Back On
As typical 2026 market ranges, vendor migration services run from roughly $15,000 for a clean, single-source portfolio of a few thousand matters to $150,000 or more for multi-source, multi-office portfolios with document migration. Internal staff time can cost as much again. Prices vary by contract and region, so confirm with vendors.
- Cost drivers: the number of source systems, volume of document attachments, custom fields, how many jurisdictions need manual register checks, and the length of the parallel run.
- Push back on: fixed-fee quotes that exclude reconciliation, "lift and shift" proposals that skip deadline recalculation, parallel runs shorter than 60 days, and contracts that don't say who owns the exception log.
Here's the decision rule. If a vendor can't show you a sample diff report and a sample exception log from a past migration in the first meeting, they're quoting for an import, not a migration. Ask for both before you shortlist.
Quick answers
How long does an IP management system migration usually take?
For a mid-sized portfolio, plan on roughly four to nine months from inventory to cutover sign-off. Register reconciliation and the parallel run take most of that time. Poor source data or many manually checked jurisdictions push it toward the longer end.
Should deadlines be recalculated in the new system or imported as-is?
Most firms recalculate statutory deadlines from verified base dates and carry over manually set ones, such as extended response periods, with a flag so they get reviewed. Recalculation shows where the old data was wrong. Carry-over keeps dates the new rules engine can't work out for itself.
Do we have to change annuity providers when we change docketing systems?
No. Many firms keep their provider and only change the integration. Either way, reconcile your case list against the provider's before cutover and confirm in writing who is responsible for anything due during the overlap.
How long should we keep the old docketing system after cutover?
Keep it read-only for at least one full renewal and annuity cycle so past decisions can be traced. Retention rules for client and matter records differ by country and by regulator, so check the period with your compliance lead or outside counsel.
Written by the Juris Tflow Direct editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.