# Real estate agency: Bitrix24 migration and portal feeds | Auspex > How Auspex is moving a Spanish real estate agency to Bitrix24: custom catalogue migration, idealista and Kyero feeds, web forms, partner feeds. Source: https://auspex.company/en/cases/real-estate-canarias/ [Case studies](https://auspex.company/en/cases/) / Real estate agency in the Canary Islands ↳ Real estate · Spain # Canary Islands real estate agency: moving to Bitrix24, migrating the catalogue and switching the portal feeds Since January 2026, Auspex has been moving a real estate agency in the Canary Islands from its in-house CRM to Bitrix24 Cloud. We set up roles, pipelines and the property card, migrated the catalogue with photos, owners and contacts, and connected the website forms. The CRM now publishes new listings to the agency’s websites; portal feeds are ready to switch. Updated 15 October 2026 Client Real estate agency in the Canary Islands Industry [Real estate · Spain](/en/industries/real-estate/) Stack Bitrix24 CloudData migration (Python)XML/JSON feeds (Windmill)Web forms + UTM ## Where did the agency start, and what had to change? The agency sells property, lets it long-term, works with new developments and sees deals through the notary and beyond. For years it ran on a CRM written for it, which held the photo catalogue, owners and clients and fed listings to portals and several agency websites. It had no rentals section, and someone who sold a flat and later bought another was entered twice. Website enquiries landed in a shared mailbox, and an administrator assigned them by hand. The rule for the move: portals and websites keep getting the same data. ## How was Bitrix24 set up for a real estate agency? After phase 0 (brief, specification, architecture), phase 1 delivered: - departments and six roles, from administrator and regional director to broker, autónomo agent and rentals manager; a regional director sees only their region; - pipelines for purchases, new developments with instalment schedules, long-term rentals, listing acquisition, after-sales services (Nota Simple, NIE, holiday-let licence) and legal support; - a property smart process with over a hundred fields: price, address and map pin, multilingual descriptions, energy certificate, commission, a rentals block, “publish on portal X” flags; - a multi-select client type: one person can be buyer, seller, tenant and landlord at once; - Gmail in CRM cards, Google Calendar, the mobile app; - two broker webinars, recordings translated into Spanish. ## How do you migrate a property catalogue from an old CRM without losing photos and links? The first idea was contacts from spreadsheets and properties from the old feeds. But deactivated properties never appear in feeds, though they can be relisted, and the property-to-owner link exists only in the database. So we read the database directly, from a read-only copy. Our migration tool is written in Python. It runs in stages from reference lists to photos and records the state of every row, so a run can restart without duplicates. A test batch of a few dozen properties came first, then the full run and a source-to-CRM check with no discrepancies. Properties with galleries, owners, contacts, companies, publication flags, original dates and authors came across. Duplicate contacts were merged into one card per person, with all their roles. Photos stay in the agency’s storage; Bitrix24 keeps links and a thumbnail. Managers got a tab mirroring the old card, with bulk photo upload and A4 printing to PDF (letterhead, choice of language) or Word. The client chose not to migrate old deals, enquiries, emails or notes. Sales start clean; the archive stays in the old system. ## How do you move property portal feeds to a new CRM without the portals noticing? The old system sent properties to idealista, Fotocasa, Kyero, pisos.com, other portals and the agency websites. Our generators on Windmill read Bitrix24 and build the same file or request with the old external IDs, so portals see the same listings. The reference is the old system’s real output from a frozen data snapshot. A comparator normalises both files, skips an agreed list of volatile fields and reports every missing, extra or mismatched value. For the websites, which receive pushed data, our own collector stood in for the live endpoints. The file feeds matched the old system byte for byte. Since September 2026, the CRM publishes properties created in Bitrix24 to the agency websites every half hour. The full cycle was tested live and caught a few differences the file comparison had missed; all are now covered by tests. ## How do enquiries from websites, email and partners reach the CRM? We connected the website forms ourselves. Each enquiry becomes a lead with its source (site and form name) and five UTM tags; errors are logged, and submissions are retried if the CRM is down. Each manager connects their own mailbox; emails land in the client’s card. Partner agencies swap listings as Kyero-format XML. A “for partners” tick adds a property to the feed for its location; sold or withdrawn ones drop out. Inbound, a Partners smart process stores their feed links, and a scheduled script pulls their properties into the main catalogue with a partner tag, without duplicates; vanished listings are archived, and an empty feed changes nothing. Both directions were demonstrated in September and are in acceptance. ## What works today, and what comes next? Phase 1 closed in July 2026. The pipelines, migrated catalogue, forms, website publishing and partner feeds work. The old system syncs into Bitrix24 hourly: only changed records update, and managers’ edits are never overwritten. Portal feeds are ready and verified; they switch as the team moves over. Three blocks await the client’s decision: a mailbox for portal enquiries parsed by AI, linking enquiries to properties with similar-property suggestions, and new developments with an availability chart. An AI layer follows. Automations come once the team works in the new system daily. ## Frequently asked ### Can a property database with photos be migrated to Bitrix24 from a custom-built CRM? Yes. Here the data came straight from the old system’s database, because deactivated properties and the property-to-owner link exist only there. ### Can Bitrix24 export properties to idealista, Fotocasa and Kyero? Yes. The generators build feeds in the format the portals already accepted, with the same external IDs, checked against the old system’s real output before the switch. ### Should the old and new CRM run a two-way sync during the transition? We decided against it: two systems writing into each other breed duplicates. A one-way sync runs instead; the switch comes when both systems’ exports match. ↳ More cases from this industry - [Residential developer Approvals and hiring were delivered in February–March 2026. The Floorix board went live in July 2026 and basic training took place in October; documents, reports and instalments are in progress.](/en/cases/residential-developer/) [CRM for this industry →](/en/industries/real-estate/) [All cases →](/en/cases/) ↳ FREE AUDIT 30 min · free · ↓ ## Ready to Get Your Sales Under Control? Free process audit — 30 minutes, and you'll receive: 1,200+ companies since 2015 · 30-day median go-live 01 A map of where you're losing leads 02 Priorities: what to automate first 03 An implementation plan for 2-4 weeks We'll call within 24 hours. The plan is yours, even if we don't work together.