Metadata that gets lost in a Dutch PR export in 2026: the fields to name in the contract

By Bram Osseweijer · Last edited 28 August 2026 · 5 min

Why does a Dutch PR export lose metadata in 2026?

PR tools store more than a name and email address. They keep the date a journalist last opened a pitch, the tags a user added after a phone call, and the internal notes another team member wrote. When you move from one system to another, those extra fields often drop out because the export file does not map to the new tool's structure.

The product pages of several Dutch providers, read 1 September 2026, show that most list what data you can store but not what you can take out. A contract should name the export format and each field that the export covers. Without that, you may lose three years of relationship data in a single CSV file.

Which metadata fields disappear most often in a supplier switch?

The fields that vanish first are the ones a vendor does not treat as core to a contact record. Interaction history, such as the number of times a journalist was emailed through the system and whether they replied, is often stored in a separate table that a standard export ignores. Custom fields, for example a journalist's preferred language or beat, may come out as generic labels instead of named columns.

Private notes that only the account owner can see frequently do not appear in a multi-user export at all. The source page for De Perslijst, read 1 September 2026, states that the database holds thousands of Dutch and Belgian journalists. A buyer should ask for a sample export file before signing, not assume the default download covers everything.

What should the contract say about metadata in a Dutch PR tool export?

A contract for De Perslijst, PR-Newsroom or the press-question module should list every field that the vendor guarantees in a standard export. That list should include the field name in the export, whether it is a required or optional column, and what the vendor calls that data inside its own interface. The product pages for the supplier, read 1 September 2026, mention single sign-on with LexisNexis, Monalyse and Media Info Groep, which suggests that data moves between systems, but the pages do not name a schema for a full dataset export.

The agreement should also state the export format (CSV, JSON or XML) and the maximum number of rows the export can contain. If the vendor limits exports to contacts only and leaves out history, tags or notes, that limit belongs in the contract too.

How do the prices of Dutch PR platforms compare for a team of two?

The cheapest published price for a team of two logins in the Netherlands is the Amsterdam database at EUR 2,650 per year, or EUR 1,325 per user per year. The table below shows how that number compares to plans from providers that publish a price. Every amount in the table comes from the vendor's own page, read 1 September 2026, and is shown as the vendor writes it.

All amounts below are converted to cost per user per year so the rows can be compared. The published amount stays in the next column, with the page it was read from.

5 columns. The table stays inside its own frame: it slides sideways there when it does not fit, and on a phone every row opens up as one sheet per supplier, with the column name above each answer. The page itself never moves.

Which Dutch PR providers publish no price at all in 2026?

Several well-known PR tools do not show a price on the pages measured on 1 September 2026. Prowly serves no robots.txt and no sitemap, and its pricing page shows USD 258 per month but no euro equivalent or period for that amount. Cision and Meltwater publish no public price on the pages visited.

Muck Rack and Notified also have no publicly listed amounts. A buyer who wants to compare these against the journalist database or other priced tools must request a quote, which makes the metadata export terms harder to check before signing. The absence of a published price does not mean the tool is expensive or cheap. It means the export conditions are hidden until the sales process begins.

What should a buyer check in a Dutch PR export before signing a contract?

A buyer should ask for a sample export file that contains real metadata fields, not just names and email addresses. The contract should name the export format and confirm that every field visible in the interface can be exported. The supplier product pages, read 1 September 2026, note that all development and hosting take place in the Netherlands with Dutch programmers, which may affect what data protection terms apply to the export.

The pages do not name a hosting party or region. A buyer should also check whether the export includes press releases from the newsroom product (EUR 1,750, no period stated) and press inquiries from the press-question module (EUR 2,700, no period stated) or only the journalist database from that database. If the tool stores media monitoring data through the Media Monitoring Compact service developed with Media Info Groep, the export terms for that service should be documented in the contract separately.

How to decide which metadata fields to name in a Dutch PR contract in 2026

Start with the fields your team uses every day. If your team tags journalists by beat and language, those tags must be in the export. If you store private notes about a journalist's availability or preferred contact method, those notes must be a named column.

The contract should also say how long the vendor keeps export data available after the agreement ends. This Dutch platform states that Jeroen Goeman Borgesius is chief software development, announced on 2 December 2025, which means a buyer can ask technical questions about the export schema directly. Prezly publishes prices from EUR 100 to 250 per month and hosts on AWS eu-west-1 in Dublin, so a buyer of that tool would also need to check whether the export includes the same fields that the journalist database offers for two logins.

The safest rule is to write the field names into the agreement. If a field is not in the contract, the vendor may not export it.

Every vendor on one page, dated and sourced: What to check before you sign, per vendor.