A multi branch feed migration should not mean weeks of duplicate listings, missing photos and staff logging into portal after portal to correct details. Whether you are bringing new offices into one group, changing CRM, replacing a website supplier or moving portal feed management, the priority is simple: keep every property live, accurate and visible while the data changes hands.
For a growing estate or letting agency, this is not just an IT task. A poorly planned migration can delay new instructions, leave withdrawn properties advertised, create inconsistent branch branding and make valuation teams question whether the new setup is ready. Get it right and your branches continue marketing without fuss while head office gains proper control over the full portfolio.
What multi branch feed migration really involves
A feed migration is the controlled move of property listing data from one source, format or distribution arrangement to another. In a multi-branch business, that data rarely consists of a single clean list. Each branch may have its own portal accounts, lead email addresses, office details, branding rules, valuation processes and historic habits for entering property information.
The migration may involve XML, BLM, RTDF or API connections. It may require an import from Jupix, Vebra or another CRM, a change in website CMS, or a move away from manually uploading stock to individual portals. The technical format matters, but the operational rules matter just as much.
For example, a group may want every branch to retain its own Rightmove or Zoopla account while centralising data administration. Another may need all listings sent from one group account, with properties allocated to the correct office by postcode or branch ID. Developers and overseas agents may also need separate feeds for new homes, international stock or specialist advertising channels.
There is no single migration model that suits every business. The right approach depends on how your branches trade, who owns the portal accounts and whether local teams need autonomy over listings. The goal is always the same: one reliable source of property data, correctly mapped to the right destination.
Start with the branch structure, not the feed file
The most common mistake is to treat a migration as a simple export and import exercise. A feed file can show property addresses, prices and photographs, but it will not automatically resolve questions about branch ownership, portal permissions or enquiry routing.
Before any live switch, establish a clear branch map. Confirm which offices are active, their public contact details, their portal account references and the listing types each office handles. Sales, lettings, commercial, student accommodation and new-build stock can all have different mandatory fields and portal rules.
This is also the time to decide what is controlled locally and what is controlled centrally. Local staff may need to create and update their own properties, while head office manages portal credentials, advertising rules and feed monitoring. That arrangement can work very well, provided the platform supports branch-level access rather than forcing everyone into a shared login.
A central dashboard gives management a practical view of the portfolio without taking everyday work away from branches. Staff can see whether an import has completed, whether a property has been accepted by a portal and whether an image or field needs attention. It replaces the familiar but costly routine of chasing several offices for updates.
Clean the data before it reaches the portals
Portal feeds expose data issues quickly. One branch may abbreviate tenure differently, another may use inconsistent property types, and older listings may contain incomplete descriptions or outdated EPC details. When data is moved at scale, these small inconsistencies become visible across hundreds of properties.
A sensible migration includes a short data review before go-live. Check that branch identifiers are present, property references are unique, prices and statuses are valid, and image URLs can be accessed. Review lead contact details too. A beautiful listing is of limited value if the enquiry lands in an unattended inbox or is sent to the wrong office.
Do not let a perfect-data ambition hold up a necessary move, though. Active properties need to be accurate first. Historic or off-market records can usually be dealt with separately. The practical question is whether a buyer or tenant would see the right price, images, description, location and branch contact details today.
For remote CRM imports, frequent checks are particularly useful. A 15-minute import cycle can keep new listings and amendments moving quickly while giving teams enough visibility to spot an exception. For manual workflows, a controlled dashboard makes it easier to update properties once and distribute those changes to every selected portal.
Protect continuity during the changeover
The live changeover is where preparation pays off. Turning off an existing feed before the replacement is accepted can leave a branch with no visible stock, or worse, can trigger a mass removal of listings. Running old and new feeds together indefinitely is not the answer either, as duplicate properties can appear.
A managed overlap is usually the safest route. The new feed is tested against a defined set of properties, portal feedback is reviewed, and branch and property references are checked carefully. Once the data is arriving correctly, the old source can be retired in a controlled order.
Pay close attention to property IDs. Where possible, retain consistent references so portals recognise an update rather than treating every listing as new. This can help preserve listing history and reduce duplication, although the exact behaviour depends on the portal and its account configuration.
Photos deserve a separate check. They are often the largest part of a feed and the most obvious sign that something has gone wrong. Confirm image order, captions, floorplans and virtual tours where used. A migration that sends the kitchen as the main image for every instruction is technically live, but commercially poor.
Make portal coverage work for every office
Multi-branch agencies often discover that their portal setup has grown organically. One office may advertise on a niche local channel, another may have an overseas audience, while head office wants consistent exposure on the major UK portals. Migration is a useful chance to rationalise this without limiting branch opportunity.
Rather than asking staff to maintain listings separately across Rightmove, Zoopla, OnTheMarket and other channels, distribute from the same approved data source. The same property information can also be prepared for international and specialist portals, including channels for student lettings, commercial properties and overseas sales.
This is where feed rules matter. A London lettings branch may need different rental fields from a Spanish resale business. A developer may want new-home availability and development information handled differently from standard resale stock. The distribution platform should support these differences without creating a new manual process for each office.
Estate Agent Feeds can centralise this work across multiple branches, with manual and remote options that fit different workflows. The point is not to force every agency into the same setup. It is to provide one dependable route from your property data to the channels that generate enquiries.
Keep support close to the operational team
A multi-branch migration tends to reveal questions that cannot be answered by a generic help page. Why has one office not received its test listing? Which account reference should be used for a recently acquired branch? Why is a portal rejecting a field that was accepted previously?
Direct phone and email support matters because the people resolving these questions are often branch administrators, lettings managers or operations staff, not developers. They need clear answers and quick action, especially when a property is due to launch or a vendor is waiting to see it advertised.
Technical teams still need proper options. APIs, XML and BLM feeds should be available where a CRM, website, app or property-management platform needs to connect directly. But the commercial team should not have to understand feed syntax to know whether their stock is live.
Build for the next branch, not just the current move
The best time to decide how a new branch will be added is before the next acquisition or office opening. A flexible setup lets you add office details, portal accounts and user access without rebuilding the entire distribution process. That keeps expansion quick and simple, whether you are moving from two branches to ten or bringing a franchise network under closer operational control.
Cost also matters. Long contracts and expensive implementation projects can make a useful operational improvement feel risky. A low-cost, pay-as-you-go model gives agencies room to test the right workflow, scale listing capacity and add feeds when there is a clear commercial reason to do so.
A well-run migration leaves your team with more than a new technical connection. It leaves them with fewer logins, clearer ownership and confidence that every branch can put the right property in front of the right audience when it matters most.