Data Migration Service

Move your existing real estate data into MLS RealtyHub through an agreed, reviewable process. The MLS RealtyHub team helps clients prepare the transition, map the supplied information, run a test import and complete the migration within a confirmed scope. This service is designed for organisations that already work with a CRM, website, portal or another data environment and need a controlled way to begin operating in MLS RealtyHub without rebuilding the agreed dataset by hand.

Your Existing Database Should Not Become a Second Job

Adopting a new platform is only part of the change. The harder question is what happens to the information your team already uses. If the old database remains separate, staff may have to export files, re-enter records and check two systems before they can continue their work. Differences between structures can make that transition harder to manage.

Data Migration Service addresses this one-time transition. The MLS RealtyHub team performs substantial migration work for the client after the parties agree what is being moved and how the source information corresponds to the destination. It is a service delivered by the team, not a self-service import button or a recurring synchronisation service.

When a Managed Migration Makes Sense

The service is relevant when an organisation has an existing body of real estate data and is preparing to work in MLS RealtyHub. The primary decision-maker is often an agency head responsible for continuity across the team, while a technical contact or another person familiar with the source data may support the migration.

It is especially useful when:

1. the agency is moving from a previous system;
2. the same information would otherwise need to be entered again;
3. the source and destination organise information differently;
4. the team needs to review a test import before the wider transition;
5. staff need training within the scope agreed for the implementation.

The Work Starts With a Defined Boundary

A migration cannot begin with the assumption that every record, field and file can be transferred as it stands. The client and the MLS RealtyHub team first discuss the scope: which existing data is relevant to the transition, what source is available and what must be considered during mapping. This makes the boundary of the work visible before the broader import proceeds.

The exact scope is agreed for each engagement. Compatibility with a particular database, CRM, website or portal depends on the source data and the agreed requirements. The type and volume of information to be moved, along with technical and commercial conditions, are confirmed before implementation.

What the Client Brings to the Process

The client provides the existing data covered by the discussion and the context needed to understand it. A person who knows how the current database is organised should also be available to clarify the meaning of the supplied information and review the proposed correspondence between the old and new structures. This means the client is responsible for:

1. identifying the source data intended for migration;
2. explaining how the current information is organised and used;
3. participating in scope and mapping decisions;
4. reviewing the test import and reporting material issues;
5. making the relevant team members available for agreed training.

These inputs are prerequisites, not paperwork added after the transfer. If the data or its meaning is unclear, the migration scope may need further discussion before the team can proceed.

How MLS RealtyHub Handles the Transition

The migration follows a deliberate sequence so that the wider transfer is not treated as an unreviewed bulk action.

1. Scope discussion. The parties establish which existing data is part of the migration and which requirements need clarification.
2. Mapping. The supplied information is matched to the relevant structure used for the agreed transition into MLS RealtyHub.
3. Test import. A test is carried out so the client can review how the agreed information appears before the broader migration continues.
4. Migration within scope. The MLS RealtyHub team imports the confirmed data covered by the engagement.
5. Training within the agreed volume. Relevant users are introduced to the working process covered by the implementation.

The team performs the migration work, while the client supplies context and confirms whether the test reflects the agreed requirements. Technical execution also depends on the client’s knowledge of what a source record means and whether it should be included.

What You Have at the End

The practical result is the agreed existing data imported into MLS RealtyHub, ready for the client to continue the relevant working process in the platform. The reviewed mapping and test import create a clear path from the previous structure to the confirmed destination instead of relying on repeated manual entry across the whole dataset.

This result is limited to the migration scope. It does not by itself establish an ongoing connection to the former system, create a recurring feed or provide a ready-made integration with a particular CRM or property portal. If information must continue moving between systems after the initial transfer, that is a separate API, feed or integration requirement and must be assessed accordingly.

A Typical Agency Transition

Consider an agency preparing to move its working property database from an older system. The agency head identifies the information that needs to be considered and appoints a colleague who understands the current structure. Together with the MLS RealtyHub team, they agree the migration boundary and mapping, then review a test import before the team proceeds with the confirmed transfer.

Once the agreed data is imported, the agency can continue the relevant work in MLS RealtyHub and complete the training included in the implementation scope. The specific steps and information included depend on the agency’s data and agreed scope.

A Short Alternative

A developer preparing to adopt MLS RealtyHub can follow the same controlled sequence for an agreed existing dataset: define the boundary, explain the source structure, review the test import and proceed with the confirmed migration. The exact information included still depends on the scope agreed for that engagement.

Migration Is Not Ongoing Synchronisation

Data Migration Service supports a transition between systems or versions. Its purpose is to move an agreed existing dataset as part of implementation. A recurring exchange serves a different need: it keeps information moving after the initial transfer and belongs to an API, data feed or integration workflow.

The distinction helps you choose the appropriate service for the work required. The wider MLS RealtyHub integration layer includes API, API-Lite, JSON and XML feeds and data services, while CRM and property portal integrations are available on request. These are separate capabilities and do not automatically become part of a migration project.

Important Scope Limits

Data Migration Service is available now, with the scope agreed for each engagement. Completion times, service levels, pricing, source formats, data volumes and compatibility with external systems depend on the specific migration and must be confirmed before work begins.

The service also does not automatically include:

1. continuous synchronisation after the migration;
2. a prebuilt connector for any CRM or portal;
3. an unrestricted transfer of every data category or file;
4. technical specifications that have not been agreed for the project;
5. custom development beyond the confirmed implementation scope.

Plan the Move Around Your Actual Data

Discuss your current data source, the information you need to bring across and the people who will review the transition. The MLS RealtyHub team can then define the migration scope and confirm the appropriate implementation route.