A feed change should not mean disappearing from the portals that generate your enquiries. Whether you are moving CRM, replacing a website supplier, adding branches or changing feed provider, an agency feed migration needs to protect the information already working hard for your business: live listings, photographs, property references, portal status and lead-generating visibility.
The technical part matters, but the commercial impact matters more. A missed instruction, an incorrect status mapping or a duplicated upload can leave a property looking unavailable, live twice or missing altogether. That creates needless calls for your team and can damage confidence with vendors, landlords and applicants.
A well-managed migration is quick and simple because it is planned around your live stock, not treated as a generic data transfer. The aim is straightforward: keep advertising moving while the new connection takes over.
What an agency feed migration actually involves
An agency feed migration is the controlled move of property listing data from one source or feed route to another. In practice, this may mean moving from a legacy CRM export to XML, BLM or API integration; changing property software; switching from manual portal uploads to a central dashboard; or bringing several branch feeds under one account.
It is not just a case of sending a file to Rightmove, Zoopla or OnTheMarket. Every portal has its own requirements, and each agency has its own way of recording property types, availability, pricing, tenure, descriptions, brochures and media. The migration must make sure the new feed speaks the right language without changing what the public sees.
For some agencies, the source is a CRM such as Jupix or Vebra. For others, it is a website CMS, in-house software, an XML feed or a spreadsheet-based workflow. The best route depends on how often stock changes, how many properties are managed and how much control the team needs. There is no benefit in forcing a technical team into manual entry, or asking a busy branch team to manage complex data files.
Start with the data your portals already receive
Before a feed is switched, establish a clear picture of the current position. This is where many avoidable problems are found. A listing may look correct on your website but have missing room information on a portal. A branch may use a local property type that needs translating. A feed may contain old image URLs or an availability field that one portal interprets differently.
Check a representative mix of live stock: sales, lettings, new homes, commercial property and overseas listings where relevant. Include properties marked available, under offer, let agreed, sold subject to contract and withdrawn. These statuses are not cosmetic. They determine whether a listing remains searchable, is removed or is displayed with the correct label.
Property reference numbers deserve particular attention. Where possible, retain the same unique reference in the new feed. This helps portals recognise an existing listing rather than creating a duplicate. If a new system generates different references, plan how records will be matched before the feed goes live.
The same applies to media. Make sure photographs, floorplans, EPC documents, virtual tours and brochures are present, correctly ordered and available through stable URLs. A migration that publishes every listing but loses floorplans is not a successful one.
Map fields before the first live upload
Field mapping is the practical work behind a stress-free migration. It links the information in your source system to the fields required by each destination. An API, XML or BLM file can be technically valid while still producing poor portal listings if the mapping is incomplete.
Descriptions, addresses, postcodes, prices, bedrooms, bathrooms and property types are the obvious fields. The less obvious fields can be just as valuable: council tax band, tenure, service charges, deposit details, furnishing status, availability date, parking, acreage, new-build development name and branch contact details.
Lettings data often needs more checking than sales data because portal rules and required disclosures vary. For example, ensure rental frequencies are correct, deposits are passed through clearly and availability dates are not accidentally shown as past dates. For overseas stock, currency, country, region and international contact details need their own mapping rather than being squeezed into UK-only fields.
A sensible migration also agrees what should happen when data is absent. Do not invent a default value simply to fill a field. It is better to identify optional fields, required fields and fields that must be completed by the branch before publication. That keeps the process accurate without making it difficult for staff.
Test in a controlled way, then switch with confidence
The safest approach is to test before asking the new feed to take responsibility for every live property. Review sample listings in the receiving dashboard and, where portal testing is available, check the public result too. Look beyond whether the property appears. Check the headline, address handling, price display, property type, image sequence, description formatting and status.
Pay close attention to update and withdrawal behaviour. Adding a new listing is only half the job. When a property is reduced, let agreed or withdrawn, the change should reach every selected portal promptly. This is the point of central feed management: your team updates one source, rather than logging into a dozen websites and hoping nothing is missed.
There can be a short overlap period during a migration, but it needs managing carefully. Running two feeds without agreed ownership can create duplicates and conflicting edits. Set a clear cutover time, identify the source of truth and stop the old feed only once the new route has been checked. If your stock changes frequently, arrange the switch at a quieter operational time and monitor the first few import cycles.
For agencies relying on frequent feed imports, checks every 15 minutes can make a real difference. A price change made during the morning should not still be waiting for publication at the end of the day. Speed is useful only when accuracy is maintained, so the first day of a migration should include active monitoring rather than a switch-and-forget approach.
Avoid the mistakes that cost enquiries
The most common migration issue is duplicated stock. It usually happens when the previous feed is still live, references change, or a portal account is connected twice. This can split enquiry history, confuse applicants and make your agency look disorganised.
The next is silent data loss. A field may not be mandatory in a feed specification but may still matter to a buyer or tenant. Missing floorplans, truncated descriptions, incorrect branch telephone numbers and removed virtual tours all reduce listing quality without necessarily generating an error message.
A third issue is assuming all portals behave identically. They do not. One may accept a particular property type while another requires a more specific category. One may publish a field immediately, while another holds it for validation. A feed partner that understands portal requirements can resolve these differences without making your branch staff learn each portal’s technical rules.
Finally, do not leave support until something breaks. Ask who will check the feed, who will contact the portal if an account setting needs changing and how quickly help is available. Direct phone and email support is particularly useful during a live change, when a small question can otherwise turn into a day of manual work.
Choose a setup that fits how your agency works
A single branch with a manageable portfolio may prefer manual entry through a central dashboard. It offers control without the cost or complexity of changing internal systems. Larger agencies, online agents and software providers will usually benefit from remote imports through XML, BLM, API, Jupix or Vebra, particularly where stock updates occur throughout the day.
Multi-branch operations need another layer of control. Branch identity, valuation areas, telephone numbers, portal accounts and access permissions should be set up correctly from the beginning. This allows head office to maintain consistent advertising while branches retain responsibility for their own instructions.
Cost should be clear as well. A migration should not lock an agency into a long contract simply because it needs dependable portal distribution. Flexible, pay-as-you-go options make it easier to choose the right level of service, whether that is a manual plan for up to 600 listings or a remote plan for up to 1,000 listings, with add-on channels available when wider exposure makes commercial sense.
Estate Agent Feeds can bring portal distribution, frequent imports and multiple source formats into one place, helping agencies move feeds without adding another admin task to the branch diary.
Keep the migration useful after go-live
The new feed route should make day-to-day advertising easier, not just solve a one-off transition. Review it after the first week. Check whether listings are reaching all required channels, whether branches understand their workflow and whether any fields are regularly left incomplete. Small adjustments at this stage can improve every future upload.
Most importantly, keep one clear source of truth for every property. When your team knows exactly where a listing is updated, portal advertising becomes a reliable part of the sales and lettings process rather than a repetitive chore. That leaves more time for instructions, viewings and the conversations that move property.