PropSpace Importer Pro connects your WordPress site directly to the PropSpace API — listings, galleries, agents and coordinates sync on their own. No XML feed, no CSV uploads, no one on your team re-typing a property at 9pm.
Built in Dubai. Runs on ordinary shared hosting.
PropSpace has been the CRM of choice for UAE brokerages since 2012, and it pushes to more than 80 portals. The one place it usually doesn’t reach automatically is the site you actually own.
So a coordinator copies each property across by hand. A villa sells on Tuesday and comes off the website the following Monday. A price drops and the site still shows last month’s number, which the buyer then quotes back to your agent on the phone.
Nobody plans it this way. It happens because the alternatives have been expensive. In Dubai, a property portal with proper CRM integration is quoted at AED 25,000 to 60,000 and up, which is a real decision for a twenty-agent brokerage — so the site gets built without the integration, and the manual work becomes permanent.
The workarounds have their own costs. XML and CSV importers break when a feed changes shape, silently skip images, and cheerfully create a second copy of a listing if a run is interrupted halfway. Duplicate listings are one of the most common complaints in real estate CRM migrations, and they are tedious to unpick once a site has a few hundred properties.
PropSpace Importer Pro takes a different route: it talks to the PropSpace API directly, and it is built to survive the hosting most agencies actually use.
Where this sits against the options a Dubai agency is usually offered.
Three things happen on a schedule you set. None of them need anyone to be watching.
The plugin authenticates against the PropSpace REST API with your own credentials, which are encrypted before they are stored. There is no feed file to host, no upload limit to hit, and no parsing failure when a field changes.
Each run compares what PropSpace holds against what WordPress already has. A listing whose price moved gets updated; the two hundred that didn’t change are left alone. That keeps a full sync light enough to run on shared hosting.
Large catalogues are processed in claimed batches rather than a single request that has to finish before PHP gives up. If a run is interrupted, the next one resumes from where it stopped instead of starting over.
Most tools that claim to import PropSpace listings read the portal XML feed. It is the easier route, and it costs you data.
The XML feed exists so portals can ingest listings. It carries what a portal needs to publish an advert and stops there. Agent mobile numbers, internal reference structures, private features, the client ID and the timestamp a record was last touched are either absent or flattened into text, because a portal has no use for them.
A feed is also a file. It is generated on a schedule, cached somewhere between PropSpace and you, and reshaped whenever the format changes. When that happens, an importer built around the old shape stops working and usually says nothing.
The REST API is the same source your CRM uses. It returns the full record, responds with a real error when something is wrong, and supports paging — which is what makes batching and resuming possible on a large catalogue.
It matters most when you want your website to do more than list properties: an agent directory with working contact details, a map that plots real coordinates, filters built on structured taxonomies rather than parsed strings. None of that is reliable on feed data.
PropSpace Importer Pro uses the API. It is why the field list below is thirty-four items and not twelve.
PropSpace serves property photos from a watermarking endpoint. The filename and its extension live inside a query parameter, so the URL path itself ends in /watermark and looks, to WordPress, like a file with no type at all.
WordPress checks the file type before it accepts an upload. Faced with something it can’t identify, it refuses — silently. No error, no warning in the admin.
The result is a sync that reports success while every gallery on the site stays empty. It is the single most common failure we see in hand-built PropSpace integrations, and it is invisible until someone opens a property page and wonders where the photos went.
Importer Pro handles these URLs properly, orders each gallery the way it is ordered in PropSpace, and leaves a manually chosen cover photo alone once someone has picked one.
Thirty-four mapped fields, stored as native WordPress post meta and ready for Elementor’s dynamic tags.
Every field is exposed to Elementor as a dynamic tag, so your property template is built the same way as any other page on your site. Property type and offering type are real taxonomies, which means Elementor’s Loop Grid filters and archive templates work without custom code.
Location is deliberately stored as plain text rather than a taxonomy. A live Dubai catalogue produces thousands of unique sub-communities, and turning those into terms makes the WordPress admin unusable within a few months. Field names are listed inside the plugin with copy buttons, so whoever builds the template isn’t guessing.
The plugin does not impose a theme. It works with Elementor, with a block theme, or alongside a premium real estate theme you already own — your designer keeps full control of the design, and the plugin is responsible only for the data being correct and current.
One honest note: scheduled syncs are triggered by site traffic unless a server cron job is configured. On a quiet site we set up a real cron during installation — it takes a few minutes and we do it as standard.
Two ways to work with us, depending on whether you already have a website you’re happy with.
Per site, per month. For agencies with a WordPress site that just needs to be connected.
One-off. A new property site built around the sync from the start.
We are taking on three launch clients this quarter at reduced project pricing, in exchange for being able to publish the result as a case study. If that suits you, mention it on the call.
No. PropSpace Importer Pro is built by Ston, an independent agency in Dubai, using the documented PropSpace API. You need your own PropSpace account and API access, which your account manager can enable.
Connecting an existing WordPress site usually takes an afternoon, and the first full import runs the same day. What takes longer is template work — if your property pages need to be designed or rebuilt around the new fields, allow two to four weeks.
Yes. Properties are stored as a standard WordPress post type with ordinary post meta, so any theme or builder can display them. Tools that map directly into one premium theme’s own property fields are faster to set up but tie your listings to that theme permanently — moving away later means re-importing everything.
Nothing is overwritten without you deciding to. Imported properties live in their own post type, so your existing pages stay untouched while you compare the two. Most agencies run both for a week, then retire the manual listings.
No. Every property is matched to its PropSpace ID rather than its title, so re-running a sync, or interrupting one halfway, updates the existing property instead of creating a second copy.
It comes off the website on the next run. There is a deliberate safety behaviour here: if the API returns an error or an incomplete response, the plugin leaves your listings alone rather than treating a network problem as everything having been deleted.
Syncing happens in the background, in small batches, and only touches records that changed. Properties are stored as ordinary WordPress posts, so your front end is as fast as any other page on the site. Image downloads are throttled so a large first import doesn’t monopolise the server.
Often not, and we will say so. If your current integration syncs reliably, keep it. The conversation is worth having when you are paying a developer each time something breaks, when galleries or agent data never worked properly, or when the person who built it is no longer available.
Yes. If you build sites for real estate clients, there is a white-label arrangement that lets you offer PropSpace integration as part of your own proposal. Ask about agency licensing on the call.
Fifteen minutes, screen shared, no slides. We connect a demo site to a sample of your catalogue and you watch the properties arrive. If it isn’t right for you, you’ll know inside the call.
The importer is one part of it. We design and build complete property websites on top of your PropSpace CRM — listing and project pages, search and filters, agent profiles — in your brand, with listings that stay in sync on their own. Tell us about your agency on WhatsApp and we will reply with a plan.