Watching migration
Import trademark watching from Excel or CSV without losing deadlines
A safe import does not start by uploading rows. It starts by identifying which data triggers work and which dates cannot be interrupted. Portfolio records, watching rules and deadlines need separate reconciliation before cutover.
Inventory the data and its meaning
Separate watched marks, variants, territories, classes, owners, clients, open alerts and deadlines. Document each status and whether a date is official, internal, estimated or merely a reminder.
Do not silently infer ambiguous values. Produce an exception list for impossible dates, duplicate identifiers, mixed fields and relationships with no match.
Prepare a stable file
Use unique identifiers, one row per primary entity and unambiguous date formats. Keep territory and class codes in dedicated columns rather than burying operational data in free-text notes.
Preserve the untouched source file and create a normalised copy with a transformation log. This makes the load repeatable and every value traceable.
Run a representative pilot
Include active matters, several territories, signs with variants, pending alerts and near deadlines. Validate counts, relationships, characters, time zones and rules with the people who use the information.
The test should produce a reconciliation: rows received, created, updated, rejected and awaiting a decision. Fixing the process is safer than manually repairing hundreds of records later.
Protect cutover and deadlines
Set a cut-off time, freeze changes or record a delta, and assign every deadline inside the window. Keep a parallel list of near-term due dates until their records, notifications and owners are confirmed.
Do not retire the previous source until counts, active rules, owners and upcoming deadlines reconcile. After launch, verify over several cycles that new publications reach the imported portfolio.
Official sources
Frequently asked questions
Is Excel or CSV better for an import?
It depends on the importer. CSV is simple and portable; Excel retains sheets and visual types. A documented schema, encoding and validation matter more in either format.
What should be migrated first?
Active matters, live rules, owners and approaching deadlines. Historical depth can follow if cutover requires it.
How do you confirm that no deadline was lost?
Reconcile every open due date before and after loading, and retain a parallel control until notifications, owners and dates are validated.