A property can look perfect in your CRM and still arrive on a portal with a missing tenure, the wrong address format or no featured image. That is usually not a portal problem. It is an estate agency data mapping problem.
Data mapping is the process that tells a feed system where each piece of property information belongs when it moves from one system to another. It turns the fields held in your CRM, website CMS or property software into the format required by Rightmove, Zoopla, OnTheMarket and other advertising channels. Done properly, it keeps listings accurate, speeds up publication and removes the daily hassle of logging into multiple portals.
For a busy sales or lettings team, this is not background technical work. It affects how quickly a new instruction goes live, how professional every advert appears and how much time staff spend fixing avoidable mistakes.
What estate agency data mapping actually does
Every property system labels information in its own way. Your CRM may use a field called “property type”, while a portal expects a specific accepted value such as detached house, flat or bungalow. One system may store a rent as a monthly figure; another needs the rental frequency stated separately. A developer may hold plot details in custom fields that are not used by a traditional estate agency at all.
Estate agency data mapping creates the rules between those fields. It can match like-for-like data, combine information from several fields, set a default where a portal requires a value, or translate internal wording into a portal-approved option.
For example, a CRM might store “freehold” under a general notes field, while a portal requires tenure in a dedicated field. If that information is mapped correctly, it is sent automatically with every relevant listing. If it is not, the listing may be incomplete, rejected or less useful to a buyer filtering their search.
The same applies to the information that makes an advert work: price, address, postcode, latitude and longitude, bedrooms, bathrooms, EPC details, council tax band, descriptions, features, images, floorplans, virtual tours and branch contact details. A feed is only as good as the mapped source data behind it.
Why accurate mapping matters commercially
Property portals are unforgiving when listings are incomplete or inconsistent. A wrong status can leave a sold property live. A missing price qualifier can confuse applicants. An incorrectly assigned branch can send a lead to the wrong office. These are small field-level errors, but they create real operational costs.
Accurate mapping helps agencies publish once and advertise everywhere with confidence. Instead of relying on someone to copy details into each portal, the CRM or central property system remains the source of truth. Make a change there and the feed passes it on at the next import or in real time, depending on the integration.
That brings three practical benefits. First, properties reach the market faster. Secondly, staff spend less time on repetitive administration and more time speaking to vendors, landlords, buyers and tenants. Thirdly, the public sees consistent information wherever they find the property.
Consistency matters particularly for multi-branch agencies. If each office uses slightly different language for property types, key features or rental terms, portal advertising quickly becomes uneven. A properly planned mapping structure gives head office control without making branch teams work through a complicated process.
The fields that need the closest attention
Not every field carries the same risk. A short feature may be optional on one portal, while a transaction type, price or property status can decide whether the listing is accepted at all.
Status, availability and transaction type
Sales, lettings, sold subject to contract, let agreed, withdrawn and available statuses need a clear mapping rule. Portals do not always use the same wording as your CRM, and the timing matters as much as the label. If an agreed property remains available for too long, it creates unnecessary enquiries and damages trust.
Lettings data needs additional care. Rent, deposit, available date, minimum tenancy length and furnishing type may all be required or expected. Mapping should distinguish monthly rent from weekly rent and ensure the correct currency and rental frequency are always supplied.
Addresses and location information
Address data looks simple until a postcode is missing, a development has no standard street number or overseas properties use a different format. A mapping plan should identify what is shown publicly, what is used for portal validation and what is retained only within the source system.
For new homes, plot number, development name and marketing address may need to work together. For overseas listings, location hierarchy can be especially important, because the portal may require country, region, province and town in separate fields.
Media, descriptions and documents
Images must arrive in the right order and at usable quality. Floorplans, EPCs, brochures and virtual tours often have their own feed fields, so they should not be treated as ordinary attachments. A great listing with a floorplan buried in the image gallery is less helpful to a serious applicant.
Descriptions need sensible rules too. Some portals accept separate short and long descriptions. Others have character limits or formatting restrictions. It is worth deciding whether your source system holds one master description or whether particular channels need tailored copy. The best answer depends on your stock and marketing process, but the core facts must remain aligned.
Start with the source data, not the portal feed
When a feed is rejected, it is tempting to focus only on the error message from the portal. Often, the faster fix is to look upstream. If staff do not have a clear place to enter tenure, council tax band or lease length, no amount of feed configuration can guarantee that information will be present.
Before mapping begins, review the fields your team actually completes. Remove duplicate fields where possible and give each important data point one clear home. If “number of bedrooms” can be entered in three places, the feed cannot reliably know which one is correct.
This does not mean forcing every negotiator through a lengthy data-entry exercise. The aim is a quick and simple workflow that captures the fields needed to market a property properly. Required fields should be reserved for information that affects publication, search results, legal compliance or applicant understanding.
It also helps to agree controlled values rather than relying on free text. For instance, a dropdown for property type prevents variations such as “Semi Detached”, “semi-detached” and “semi detached house” from producing inconsistent results. Free text still has a place in property descriptions and feature lists, but structured information should be structured at the source.
Mapping across portals is not always one-to-one
A common mistake is assuming that one CRM field always maps directly to one portal field. Sometimes it does. Often it does not.
A portal may require a value that your system does not hold, or your system may contain valuable information that has nowhere to go on a particular channel. Some portals have specialist requirements for commercial property, student lettings, new homes or international stock. Certain channels use their own category lists, image rules and mandatory fields.
That is why a feed setup should be tested against the portals you actually use, rather than built around generic assumptions. Rightmove feeds commonly use RTDF or BLM formats, while other connections may work through XML or API workflows. The format changes, but the principle does not: each destination needs a clear translation of your property data.
There are trade-offs. A highly customised mapping can give a developer or software provider precise control over complex stock, but it needs documentation and testing when new fields are introduced. A simpler standard mapping is quicker to launch and easier for an independent agency to maintain. The right option depends on the volume and variety of your listings, not on using the most complicated setup available.
A practical process for getting mapping right
Start by listing the systems involved: the CRM or source software, your website, each portal and any advertising channels such as social media or classified sites. Then identify which system owns each item of data. Avoid situations where a price is edited in one place, the description in another and the property status somewhere else.
Next, map the mandatory basics first: branch, reference number, transaction type, status, price, address, property type, bedrooms, descriptions and media. Once these are working, add the fields that improve search visibility and listing quality, such as tenure, EPC information, floorplans, video and key features.
Test with real examples, not just a blank sample property. Use a typical sale, a typical rental, a property with a price reduction, a withdrawn listing and, where relevant, a new-build plot or overseas home. Check the published advert on each destination, including how photos display, which office receives the lead and whether changes arrive as expected.
Finally, give one person or team responsibility for reporting issues. A clear route for questions prevents staff from making manual portal edits that later get overwritten by the next feed import.
Keep the mapping under review
Data mapping is not a one-off job. Portals change their requirements, agencies add new branches, CRMs introduce fields and regulations can alter the information consumers expect to see. A feed that worked perfectly last year may need adjustment after a software update or a change in stock mix.
Regular import checks are a sensible safeguard. Reviewing feed activity every 15 minutes, where frequent imports are available, means issues can be picked up before a valuable instruction spends a day missing from the market. Watch for rejected records, empty mandatory fields, duplicate listings and media failures.
Estate Agent Feeds can manage this translation between your existing CRM, XML, BLM, API or manual-entry workflow and a wide range of portals, without asking your team to become feed experts. The practical aim is no fuss: keep property details accurate in one place, then send them where they need to go.
A well-mapped feed gives your agency something more useful than another technical process. It gives your team the confidence to win an instruction, load it once and get on with the work that actually grows the business.