Data Source API / CRM Properties Import

Modern real estate teams rarely operate from a single piece of software. Property data may begin in a CRM, pass through a corporate network, feed a website or portal, and then move into specialist platforms used to manage auctions, offers and buyer engagement.

The quality of that connection matters. When listing information can move directly between systems, administration teams spend less time re-entering property data, workflows become more consistent and the risk of information being entered differently across multiple platforms is reduced.

RE Software already supports more than 20 publicly listed CRM, API, MLS and aggregator integrations across its platform. However, the integrations displayed publicly are not the full picture. RE Software also works directly with corporate groups, networks and organisations that operate their own property technology, including integrations that are developed specifically for those environments and are not publicly advertised.

What if your CRM is not currently supported?

If your business uses a CRM, MLS, aggregator or proprietary network platform that is not currently connected to RE Software, that does not necessarily mean an integration is unavailable.

RE Software is open to assessing new integrations where there is a clear subscriber requirement and a practical way for the systems to exchange the necessary property information.

How integrations can be structured

The way an integration is approached will depend on the system being connected, the information available and the workflow the subscriber is trying to achieve.

In many cases, the connection may be established through an API. In other environments, particularly within established Australian real estate software workflows, XML may provide the appropriate method of transferring property information.

For larger corporate groups or networks, the integration may instead connect directly with an internal property platform or central data source operated by the organisation.

• ●API connections can allow structured property data to be exchanged between supported systems.
• ●XML can support property data feeds where that format is available from the subscriber's CRM or technology provider.
• ●MLS and aggregator connections may provide another pathway where property data is already being distributed through a central source.
• ●Corporate and network integrations can be assessed for organisations operating their own internal property software or centralised data environment.

The appropriate method is determined during the technical assessment rather than assuming every system should be connected in the same way.

What the integration should achieve

For most agencies, the primary objective is straightforward: make it easier to import an existing property listing directly into the RE Software platform without rebuilding the property manually.

Depending on the available data and the agreed integration scope, this may include information such as the property address, listing details, selling agents, images and other property information required to prepare the campaign.

Once the property is available within the platform, the team can continue with the relevant Auctions Live or Offers Live workflow rather than using the integration as a replacement for the agency's CRM.

This distinction is important. The CRM remains the agency's core property system, while RE Software provides the specialist environment used to manage auction, offer and related sales workflows.

Why an introductory development meeting is required

New integrations require some planning before development can begin. Even where two systems both provide API access, there can be differences in field structures, authentication, property statuses, office structures, agent records and the way data is made available.

For this reason, subscribers requesting a new integration are required to first schedule an introductory online session with the RE Software development team.

The purpose of the session is to understand the intended workflow, identify the available data source and determine the most appropriate technical pathway before any development work is scoped.

• ●What system or data source needs to connect with RE Software.
• ●Whether an API, REAXML feed or another approved integration method is available.
• ●Which property information needs to be imported.
• ●How offices, agents and listings are structured within the source system.
• ●Whether the integration is intended for a single office, multiple offices or an entire corporate network.
• ●Any technical, security or access requirements that need to be considered before development commences.

Schedule an introductory online session with the RE Software development team.

What happens after the initial discussion?

Once the intended workflow and technical requirements are understood, the RE Software team can assess what is required to establish the connection.

Where an existing integration pathway can be used, the process may primarily involve configuration and access. Where a new connection, data mapping or development work is required, the team will need to review the scope before confirming the next steps.

Testing is also an important part of the process. Property data needs to be mapped correctly, the expected listing workflow needs to be confirmed and the connection should be validated before it becomes part of the subscriber's normal operating process.

This planning is particularly important for larger networks, where a seemingly simple property import may need to account for multiple offices, different user structures, centralised administration or organisation-specific rules.

Are there fees for a new integration?

Fees may apply where development, configuration or other technical work is required to establish a new integration.

Whether fees apply will depend on the work involved and the subscriber agreement held with RE Software. The technical and commercial requirements can therefore be considered once the proposed integration has been reviewed with the development team.

This approach allows the scope to be understood before assumptions are made about the complexity or cost of the work.