From an outdated .NET solution to a custom property platform for Norsk Megling International

Norsk Megling International was working with an older .NET-based solution that no longer supported the business. OceanEdge built a new custom platform with Next.js, Sanity and Mapbox.

Propertylisting

Norsk Megling International was working with an older .NET-based solution that no longer supported the business well enough. The platform felt outdated, was difficult to navigate for users and cumbersome to manage internally. For a company handling a large number of properties across multiple locations, a visual refresh alone would not have been enough. The structure itself had to be rebuilt.

OceanEdge approached the project as more than a website redesign. This was a migration, a restructuring effort and the build of a new custom platform for property search, content management and day-to-day administration.

The goal: A modern platform for operations and growth

The goal was to replace the old setup with a modern platform that would be easier to run, easier to navigate and better prepared for future growth. That meant improving both the public-facing experience and the way properties, images, locations, broker information and content were handled internally.

The new solution was built with Next.js on the frontend and Sanity as the headless CMS. Property images were moved to Cloudflare R2, and map functionality was built with Mapbox. But the real value was not the stack itself. It was how the stack was used to create a more structured platform around a complex property model.

Migrating a large data volume

The project included migrating a large volume of property data from the old solution into a new structure. Properties, images, locations, statuses, broker data and content all had to be extracted, cleaned, mapped and moved. This was not a simple export. It required data cleanup, normalization and custom migration scripts to make the content usable in a more robust setup.

A key part of the work was building a clearer content model in Sanity. The new structure made it possible to organize properties, locations, brokers, blog content and homepage settings in a single, more controlled workspace. That gave the client a much stronger foundation for day-to-day operations than the old system.

A structured property experience

On the frontend, a more structured property browsing experience was built. Users can filter, browse listings and use map-based navigation to get a clearer overview of available properties. The URL structure was also rebuilt around country, region, city and property, creating a cleaner experience for users and a more logical structure across the platform as a whole.

The property detail pages were designed to make the content easier to understand and the next actions more obvious. Gallery, key information, location and contact points were brought together in a setup that supports both presentation and follow-up.

New Property ListingOld Propertylisting
Dra for å sammenligne

Administration and internal structure

Internally, the administration side was just as important as the public-facing site. The new platform made it possible to work more clearly with statuses such as available, reserved and sold, and to follow up on listings missing location data, broker data or images. This is the kind of structure that often goes unnoticed on the surface, but becomes highly valuable once the platform is used over time.

Map view and filtering were also central parts of the project. Instead of relying on a simpler and older search flow, the new platform introduced a more modern listing experience with maps, filters and a clearer overview of properties across locations.

A structure problem, not just a design problem

For OceanEdge, this project is a strong example of what happens when a project is treated as a structure problem, not just a design problem. The old solution did not simply need to look better. It needed to work better, be easier to manage and provide a stronger foundation for continued operations.

The project also shows the difference between a standard website and a custom solution. When content, images, locations, statuses, search and administration all need to work together, adding a new design layer on top of an old setup is rarely enough. The system needs to be rebuilt properly.

The result

The result was a new platform for Norsk Megling International with better structure, easier administration and a clearer user experience. Not as a template-based website, but as a custom solution built around how the business actually works.

For companies that have outgrown standard solutions, this is often the real need. Not just a new website, but a better way to organize content, workflows and digital touchpoints.