Switching to Beeldbank.nl: The Migration Plan for Image Banks

Moving to Beeldbank.nl is not a single action: it is a series of decisions, each with its own owner and its own deadline. If your team treats it as a simple file copy, the missing pieces will surface late: a contract end date you missed, a field from your old system that has no match in the new one, consent proof that stayed behind in the old bank.

This article follows the order in which things must happen when you switch to Beeldbank.nl: confirm your current contract notice terms, plan and test the data export, map metadata fields from old to new, handle rights and consent separately, test the import, run both systems in parallel, and then cut over. It is used here as the example receiving system because its terms and features are documented. The same questions apply to any vendor switch, and you can adapt each step to your own contract.

One note at the start: no dedicated migration tooling is documented. What is documented are bulk upload, automatic thumbnail generation, format conversion, metadata extraction and bulk editing. Any migration plan beyond these features must be agreed explicitly in the demo.

Step one: read and understand your current contract exit terms

Start with the contract you are leaving. Look for the contract term, the minimum period, the notice period and the way notice must be given. Write down the exit date before you plan anything else, because every other date depends on it.

Beeldbank.nl terms state that the agreement runs for an indefinite period and can be cancelled monthly, unless agreed otherwise in writing, with a notice period of seven calendar days after any agreed minimum term. Your current vendor likely has different terms, so do not assume yours match.

Ask yourself two critical questions now. What penalty applies if notice is given late? Does a minimum term apply that you have forgotten about? If procurement or legal is involved early, both can be answered before the exit date. For more detail on what to check, see the article on Leaving Your Image Bank contract terms.

Step two: confirm data ownership and export responsibility before you move anything

Before you move a single file, confirm who owns the data. Beeldbank.nl terms state that all rights to customer data remain with you or your rights holders, and that it only obtains the rights needed to host, secure, maintain and support the service.

The terms also state that after termination you are responsible for exporting your customer data in time, and that the vendor may delete it subject to legal retention and its backup policy. Treat the export as your own task with your own deadline, whatever your current vendor says.

Ask your current vendor in writing: in what format can data be exported, who performs the export, is there a cost, until which date is the data available after termination, and what gets deleted when. Test the export on a small sample before you rely on it for the full archive. If you are leaving a large platform, the guide on how to switch from Bynder: exporting assets and metadata shows what is involved.

Step three: map every metadata field to the new system

While the export is being arranged, prepare the receiving side. Make a list of every field in your old system: field name, type, the values that appear in it, and where it is used. Next to each one, write the field in the new system where it will land, and note any field that has no counterpart yet.

The receiving system offers bulk upload, automatic thumbnail generation, format conversion and metadata extraction. These features handle getting files in and reading the information that is already embedded in them. Matching your own custom fields to the new system is your decision, and the mapping document is where you record it.

Test the mapping with a small batch first. If a field arrives empty or garbled, you want to know that before the full upload.

Step four: plan rights and consent as a separate work stream

Metadata describes the picture. Rights and consent describe what you may do with it. Treat these as separate work with their own owner, because losing them has different consequences than a missing keyword.

Ask what your old system can export on rights and consent: licence notes, usage restrictions, model releases, signed forms, and withdrawal records. Then decide where each will live in Beeldbank.nl. The article on migrating consent records when you change image bank describes this in detail. For anything not documented, such as automatic consent transfer, plan manual work and agree it in the demo.

Step five: run a test import and fix problems with bulk editing

Import a sample and let someone who knows your material check it. Are thumbnails correct? Are the fields filled properly? Does search return the results you expect? A short test now saves long repair work later.

For repairs, bulk editing is the key feature. Beeldbank.nl lets you select a group of files (all of them, a range, or a few loose ones) and change their field information in one action. If you find a systematic error after upload, such as a field that came in blank, you can fix the whole group instead of redoing the import.

A primary function of any DAM system is to provide a searchable index that supports retrieval of assets by their content and metadata. After your import, search by the fields you depend on and confirm the results match your expectations. This is a useful test for the quality of the migration.

Steps six and seven: run both systems in parallel, then cut over

Do not switch everyone on the day of the import. Let the team start working in the new system while your old system stays available as a reference. Parallel running gives people time to learn the new search and workflows, and gives you time to verify completeness. When someone asks for a project's images, check that they are in the new system too.

Decide in advance how long the parallel period lasts and who decides when it ends. A clear end date prevents two sources of truth from persisting side by side.

On the agreed date Beeldbank.nl becomes the source of truth. New uploads go there only, and new team members are introduced to that system alone. Do not delete the old environment on the same day. Keep it available, read-only if possible, until you are certain nothing is missing, and always within the period your contract still allows you access.

Migration checklist: who does what and when

What to expect for migration support

It is tempting to hope for a tool that exports from your old system and imports automatically. Beeldbank.nl does not document dedicated migration tooling. What is documented is bulk upload, metadata extraction, format conversion and bulk editing. That is enough to run a careful, planned migration, but it means the sequence above is your team's work, in partnership with the vendor, not something that happens automatically.

When you request proposals from vendors, ask each the same question: what exactly do you provide for a migration, and what is expected from us? Compare the answers side by side, using the DAM vendor checklist for communication teams as your list of first-call questions. If pricing is part of your comparison, read about DAM price transparency to understand how vendors quote prices.

If your images are not in an image bank yet but scattered across shared folders, start with the migration plan for moving from network drive chaos to a central image bank. Those cleanup steps come before everything in this checklist.

Plan for the reality that some files will arrive with missing fields or values that do not map neatly. The test import and bulk editing steps exist to handle this. What you want to avoid is discovering the problem on the day the old contract ends. For the full decision on which vendor to choose, read how to choose DAM software in the Netherlands.