Trademark Docket Migration: 12 Critical Checks

Every published guide to trademark docket migration is a project-management document. Form a team. Clean the data. Test in a sandbox. Train the users. That advice is sound, and it is also silent on the only thing that can cost a client a registration: whether the dates that arrive in the new system are the dates the law actually requires. A migration moves records. It does not move obligations, and it does not recompute them. This is the verification layer the literature skips — twelve checks, each tied to a statutory clock and an authoritative source you can confirm it against.

Why Trademark Docket Migration Breaks at the Date Layer

A docketing record has two halves that behave completely differently under a move. The first half is descriptive: mark, owner, serial number, registration number, class, status, correspondence address. That half is portable. It is text and numbers, it maps field to field, and a competent vendor will move it accurately.

The second half is derived. A Section 8 due date is not stored knowledge — it is a conclusion computed from a registration date under a rule. So is a renewal window, an office action response date, and a Madrid dependency expiry. When those values move as literal dates in a spreadsheet column, they arrive stripped of the rule that produced them. They look authoritative in the new system precisely because they no longer show their working.

This is why a trademark docket migration can pass every test a migration plan specifies and still be wrong. Record counts reconcile. Spot checks match. Nothing in that process asks whether the date in the source was correct to begin with, or whether the rule that generated it still applies. A migration is the moment an inherited error gets laundered into a fresh system with no audit trail.

The failure is also asymmetric. An error in the descriptive half is visible — a misspelled mark or a wrong class gets noticed by the next person who opens the file. An error in the derived half is invisible until the date passes. That is the specific risk a trademark docket migration carries and a general data migration does not, and it is why the verification pass has to be organised around clocks rather than around records.

What the Published Migration Guides Cover — and What They Leave Out

We read the pages that currently rank for docketing migration advice before writing this one. They are genuinely useful within their scope, and the scope is consistent across all of them: people, sequencing and hygiene. None of them, on the pages we reviewed, states a single trademark statutory deadline.

Alt Legal’s migration guide organises the work into communication, data organisation and data provision, and makes a good point about using the move to retire abandoned marks and departed timekeepers. JuraLaw covers migration team roles — team lead, IT manager, docket manager — and sandbox review. Black Hills AI is the closest to the date layer, treating file transfers, on-docketing and de-docketing as distinct risk moments, though its treatment is patent-oriented.

What the migration literature covers well	What a trademark docket also needs before go-live
Assembling a migration team and assigning approvals	A named practitioner who signs off that recomputed dates are legally correct
Cleaning out abandoned marks and inactive clients	Confirming ‘abandoned’ against the register, not against internal status flags
Exporting to a standard format and mapping fields	Re-deriving each maintenance window from the registration date and filing basis
Reviewing migrated records in a sandbox	Branching Section 66(a) matters, which follow different response rules
Training docketing staff and attorneys separately	Carrying the Madrid five-year dependency date, which many systems never stored
Confirming record counts reconcile	An exception report of every date that changed when recomputed, with a reason

This is not a criticism of those vendors. A migration provider can reasonably say that legal date correctness belongs to the firm, and it does. The gap is that nobody publishes the firm’s half of the work, so it is the half that tends to go unscoped, unbudgeted and unassigned.

The Five Statutory Clocks That Must Survive the Move

Before touching an export file, write down which clocks the portfolio actually runs on. For a US-centred trademark portfolio there are five, and each has a different source of truth and a different failure mode under migration.

Clock	The rule	Where to verify it
Section 8 declaration of use	Between the fifth and sixth years after the registration date; six-month grace period with an additional fee	USPTO
Section 9 renewal	Between the ninth and tenth years, then every ten years — 19–20, 29–30, and so on; combined with Section 8	USPTO
Section 71 (Madrid-based registrations)	Replaces Section 8 for registrations with 79-series serial numbers, on the same 5–6 and 9–10 year windows	USPTO
Section 15 incontestability	Optional; after five consecutive years of continuous use post-registration, filed within one year of the end of that period	USPTO post-registration
Office action response	Three months from issue, with one three-month extension for a fee, since 3 December 2022; Section 66(a) is six months with no extension	USPTO
Madrid dependency	Five years from the date of the international registration under Article 6(3); transformation within three months of cancellation under Article 9quinquies	WIPO Lex

Note the asymmetry in that table. Sections 8, 9 and 71 run off a registration date the system already holds, so they survive a migration reasonably well — if the registration date itself came across correctly. The other three do not run off anything the new system can see, which makes them the ones to verify by hand.

Recomputing Maintenance: Sections 8, 9 and 71

Start here because it is the highest-volume check and the easiest to automate. For every live registration, the maintenance windows are a pure function of the registration date. Recompute them from that date rather than importing the due-date column, then compare the two and investigate every difference.

The USPTO states the windows plainly: the Section 8 declaration is due between the fifth and sixth years after the registration date, with a six-month grace period available on payment of an additional fee. The Section 9 renewal is due between the ninth and tenth years and every ten years thereafter, combined with Section 8 in each of those windows.

Two migration-specific traps sit inside that simple rule. The first is the grace period. Some legacy systems docket the grace deadline as the deadline, because it is the last possible date. If those records migrate and the new system recomputes from the registration date, you will see a six-month shift across a whole cohort and it will look like a migration bug. It is not — it is a disclosure of how the old system was configured, and the recomputed date is the one to keep.

The second is Section 71. Registrations that came through the Madrid Protocol carry 79-series serial numbers and file their continued-use declaration under Section 71 rather than Section 8, on the same schedule. If the old system stored a generic “Section 8” event type for everything, the filing basis distinction is gone from the data and has to be reconstructed from the serial number. That reconstruction is straightforward and almost nobody scopes it.

If the portfolio has not been reconciled against the register recently, run a trademark docket audit before the export rather than after the load. Migrating a portfolio you have not audited simply moves the unknowns into a system where they are harder to attribute.

The Office Action Clock Changed in December 2022

This is the check most likely to find something, because the rule changed recently enough that a single portfolio can contain records created under both regimes.

Under the Trademark Modernization Act, the USPTO implemented a three-month deadline to respond to office actions issued during examination on 3 December 2022, for applications based on Section 1 (use in commerce or intent to use) and Section 44 (foreign application). An applicant may request a single three-month extension for a fee, which carries the response deadline out to six months from the issue date.

The critical branch is Madrid. Section 66(a) applicants are expressly excluded from that regime: they respond within six months of the issue date, with no option to extend. A docketing system that applies a uniform three-plus-three rule to every matter will therefore be wrong on Section 66(a) files — conservatively wrong, which is survivable, but it also means the file gets worked on a schedule nobody chose.

A system that applies a uniform six-month rule to everything is wrong in the dangerous direction. That configuration was correct before 3 December 2022 and silently became a three-month overstatement afterwards. An office action issued on 2 December 2022 kept its six-month period; one issued a day later did not.

• Pre-December 2022 records: confirm whether any open response deadline was computed under the old six-month rule and is still being relied on.
• Section 1 and Section 44 matters: three months base, one three-month extension available for a fee, so the docket needs both the base date and the extended date as distinct events.
• Section 66(a) matters: six months, no extension — the extension event should not exist on these records at all.
• Expungement and reexamination office actions: three months to respond with a one-month extension available for a fee — a different extension length from examination office actions, and a common configuration miss.

Because the extension is a request rather than an entitlement, the cleanest configuration dockets the base response date as the real deadline and the extended date as a conditional follow-on that only activates when the extension is actually filed. We go through the mechanics in more depth in our guide to the trademark office action deadline.

Madrid Dependency: The Five-Year Clock Your Old System May Never Have Held

Most US-configured docketing systems handle Madrid registrations as ordinary registrations with an unusual serial number. That works for maintenance. It fails for dependency, because dependency is not a filing deadline — it is a vulnerability window, and there is nothing to file at the end of it.

Under Article 6(3) of the Madrid Protocol, an international registration remains dependent on the basic application or registration for a period of five years from the date of the international registration. If the basic mark falls within that window, the international registration falls with it across every designated territory — the outcome practitioners call central attack. The treaty text at WIPO Lex is the source to cite.

What follows is a real deadline. Article 9quinquies allows the former holder to transform the cancelled international registration into national or regional applications, but the transformation application must be filed within three months from the date on which the international registration was cancelled. A transformed application is treated as though filed on the date of the international registration, so priority survives — if the three-month window is caught.

For a trademark docket migration this produces two concrete requirements. Carry a dependency expiry date for every international registration, computed as five years from the international registration date, and flag the underlying basic application or registration so that any adverse action on it triggers review of the international file. Neither is a field most systems ship with, which means it survives a migration only if somebody asks for it.

If the portfolio is materially Madrid-based, our breakdown of Madrid Protocol deadlines covers the wider set of dates that need to exist in the target system before cutover.

The 12-Point Trademark Docket Migration Verification Plan

This is the pass to run after the data has loaded and before the old system is switched off. It is deliberately organised by clock rather than by record, because errors cluster by rule, not by client.

• Reconcile the population first. Count live registrations, pending applications and international registrations in source and target. A trademark docket migration that loses a category is easier to spot as a count than as a missing date.
• Verify status against the register, not the export. Pull current status from TSDR for every record. Internal status flags drift; the register does not.
• Recompute every Section 8 window from the registration date. Compare against the migrated due date and list every discrepancy.
• Recompute every Section 9 window on the same basis, including the ten-year repeats beyond the first renewal.
• Split Section 71 records out by 79-series serial number and confirm the event type is correct rather than a generic Section 8.
• Check whether grace-period dates were docketed as primary deadlines in the source, and normalise to the statutory window with the grace date as a secondary event.
• Identify every open office action and recompute its response date under the rule in force on its issue date.
• Branch Section 66(a) matters to six months with no extension event, and confirm no extension deadline was inherited.
• Add a Madrid dependency expiry five years from each international registration date, and link the basic mark.
• Capture Section 15 eligibility windows for registrations approaching five years of continuous use, as an opportunity event rather than a compliance deadline.
• Confirm correspondence and email of record for every matter, since a migration often coincides with a change of firm or attorney of record and a notice sent to a stale address still starts the clock.
• Produce a signed exception report. Every date that changed on recomputation, with the reason and the authority. This is the artefact that makes the migration defensible.

Twelve checks sounds heavy until you scope it. Eleven of them are queries over the loaded data set, and only the office action review genuinely requires file-by-file judgement. On a portfolio of a few thousand marks this is days of work, not weeks — and it is the only part of a trademark docket migration that produces evidence you did it right.

Parallel Running: How Long to Keep Both Systems Live

The migration plans we reviewed all recommend sandbox testing before go-live. Few say anything about what happens after. The answer that protects a portfolio is to keep the outgoing system available read-only well past cutover, because the verification value of the old system is highest precisely when a date in the new one looks surprising.

A workable rule: retain read-only access through at least one full quarterly docket cycle and one complete office action response, from issue to filed response. That spans enough event types to exercise the configuration on real matters rather than on test data, and it gives you somewhere to look when a due date does not match what the file history suggests.

Export the old docket to a static, human-readable archive before access ends — a dated report per matter, not a proprietary backup you cannot open without a licence. The firm’s data belongs to the firm, and a plain archive is what makes that ownership practically useful two years later when a question arises about what was docketed and when.

Resist the temptation to run both systems as live systems of record. Dual entry creates divergence and, worse, ambiguity about which docket governs. One system of record, one read-only reference.

Verify Against the Register, Not Against Your Old Docket

If there is one habit that separates a safe migration from a lucky one, it is the choice of comparison baseline. Reconciling the new system against the old system answers a narrow question — did the transfer work — and guarantees that any error already in the old system is preserved perfectly.

Reconciling against the register answers the question that matters: is this date right. For US matters that means TSDR for status, registration date and prosecution history. For international registrations it means the WIPO records for the international registration date and designations.

There is a practical dividend here beyond correctness. A register-based reconciliation catches the things that changed while the migration was in flight — an office action issued, a registration certificate that issued, a designation refused. Migrations take weeks, and the register does not pause for them.

Everything in this verification plan is the same discipline that prevents the routine failures we catalogue in trademark docketing errors. A migration simply compresses every one of those failure modes into a single window, which is why a trademark docket migration deserves the verification pass it rarely gets.

How PerspireIP Can Help

A trademark docket migration is not a software project with a legal footnote. It is a legal verification exercise that happens to involve software. The firms that come through one cleanly are the ones that treated the post-load reconciliation as billable professional work rather than an IT acceptance test.

PerspireIP runs managed trademark docketing for firms and in-house teams, including migration reconciliation: independent recomputation of maintenance windows, office action branches and Madrid dependency dates against the register, delivered as an exception report you can act on. If you are mid-move or planning one, we can run the verification pass in parallel with your vendor.

Frequently Asked Questions