Drupal to WordPress for New Mexico Cultural Organisations: Preserve Collection Context
A migration planning guide for collection websites where context and relationships matter as much as page appearance.
In this article
Illustrative workspace. Screens show concepts, not a delivered client system.
Moving a cultural collection website is not just a matter of copying attractive images into a new gallery. An object may have a catalogue reference, creator relationships, attribution, related exhibitions and restrictions on what can be published. For New Mexico cultural organisations considering Drupal to WordPress, begin with a representative collection record. Establish what must survive the move and what should remain in the authoritative collection system before estimating a redesigned public website.
Find the authoritative collection record
Determine whether Drupal stores the collection itself, presents information from another system or combines editorial pages with imported records. The new website does not automatically need to become the master database. Identify the owners of object data and approved public descriptions.
Create a mapping for a representative object and its related creator, exhibition and media records. Preserve stable identifiers where they are meaningful. This makes it possible to review relationships and investigate missing records without relying only on page titles.
Separate public interpretation from restricted information
Not every catalogue field belongs on the public website. Ask the organisation to identify the approved public subset, attribution wording, image permissions and any records that need restricted handling. The migration team should implement those decisions rather than infer publication rights from an existing upload.
New Mexico’s arts and culture information supplies audience context, not rights clearance for a specific collection. Content and rights decisions require the organisation’s authorised reviewers. The project should record their decisions in a practical field and media mapping.
Choose a content model editors can maintain
Use structured relationships where the same creator, exhibition or collection appears in multiple places. Use native editable page components for the public presentation where appropriate. Avoid flattening everything into independent page-builder text that staff must repeatedly correct.
WordPress’s export documentation describes its own content export format. It is not a complete cross-platform migration plan. Drupal field types, referenced entities, files and any custom integration must be assessed against the actual source installation.
Keep existing discovery paths connected
Inventory public object URLs, category pages, exhibition pages and document downloads that people already use. Decide which destinations will remain, which will change and how discontinued material will be explained. A broad redirect to the homepage loses the context someone was seeking.
Review search and filtering against collection language approved by the organisation. Test a record reached through search, through an exhibition and through a related creator. Confirm that credits and meaningful captions remain associated with the correct media in each view.
Use a pilot collection to price the migration
Select records that expose the difficult cases: multiple creators, missing images, related exhibitions and restricted fields. Ask for a migration demonstration and reconciliation notes before accepting a fixed price for the entire archive. Define how a corrected source record reaches the final migration.
Can all Drupal features move unchanged? The content can be assessed for transfer, but custom behaviour may need a supported replacement or rebuild. The Drupal migration planning guide explains the broader content, redirect and launch decisions. Agree an editorial review owner before release.
Discuss your implementation
Share the current Drupal site, a sanitised collection record and the systems that own the authoritative data. I can assess a WordPress public-site rebuild with a defined migration and editorial review scope for your New Mexico organisation.
I’m Jagjeet Singh, an India-based developer working remotely with businesses and agency teams. Discuss your cultural website migration. Share the existing website or workflow and the decisions holding the project back. I can assess the requirements, recommend a suitable implementation approach and propose a defined scope. Working hours and review milestones can be agreed with your team.
Written by
Jagjeet Singh
Full stack development, WordPress engineering and practical web products. I work with businesses, teams and agencies in India and worldwide.
Explore my work
