'%20d='M0%208a8%208%200%200%201%208-8h24a8%208%200%200%201%208%208v24a8%208%200%200%201-8%208H8a8%208%200%200%201-8-8V8Z'/%3e%3cpath%20fill='%23fff'%20d='M10.41%206v3.779h15.048v19.537h4.132V6H10.41Z'/%3e%3cpath%20fill='%23fff'%20d='M20.967%2034V13.837L10.41%209.78v20.166L20.967%2034Z'/%3e%3cdefs%3e%3clinearGradient%20id='reapit-sales__a'%20x1='20.702'%20x2='20.702'%20y1='.351'%20y2='31.228'%20gradientUnits='userSpaceOnUse'%3e%3cstop%20stop-color='%235573FD'/%3e%3cstop%20offset='.575'%20stop-color='%234E56EA'/%3e%3c/linearGradient%3e%3c/defs%3e%3c/svg%3e)
Migrating your Data into Another Reapit Sales Account (RS to RS)
In this article, we'll cover migrating your Reapit Sales data into another Reapit Sales account.
Migrating your Data into Another Reapit Sales Account (RS to RS)
In this article, we'll cover migrating your Reapit Sales data into another Reapit Sales account.
Existing Reapit Sales users may come across the scenario that they will be migrating into another Reapit Sales system or an Reapit Sales centralised database system.
Working in a shared database: A shared database is one that allows multiple offices to work within one specific Reapit Sales system, allows enhanced contact accessibility, whilst still being able to maintain their office level privacy. A shared database is one of which is established its own configuration standards, which therefore means your permission set may deviate from your previous Reapit Sales system. Typical system deviations can include:
Staff Permissions
Contact Database Ownership Configuration.
Systems data sharing preferences (Open VS Closed accessibility and functionality).
Data cleaning tips
Should an agency migrate into a non-centralised database system and, if assigned as a master user, they will be able to control the configuration of the new system.
What's in scope for my Reapit Sales to Reapit Sales (RS to RS) Data Import?
There are 3 types of AB to AB migration scopes that you will be advised on.
Option 1: Full AB to AB scope.
Note: Commissions are excluded if the source and target system are not compatible.
Option 2: AB to AB excluding commissions (used when the source and target system have incompatible commission deductions/configuration settings).
Option 3: Complex AB to AB option may be used when the following three scenarios appear:
Not on REA: Listings were not on portal fed to REA, so therefore the source cannot be matched into the new system.
Ownership/Approval: The incoming party does not own or have approval to import listing data. This would cover instances where the office was not allowed to keep the listings i.e., business purchase, and where an agent is leaving and they don't own the listings. It is important to note that appraisals are included, it is typically the alternate listings that will excluded such as for sale/ lease.
Early REA Import/Transfer: Instructions were not followed, and an REA import/transfer has been completed prior to the import to the new system (Data always comes first, and then an REA listing import second).
The below features will be included in a full AB to AB Scope (Option 1):
Agents
Generic information + web profile.
Contacts
Contact categories.
Contact requirements (suburbs & regions).
Communication history (doesn't include template preview, just basic history).
Inspection history.
Enquiry history.
Related Agents.
Notes.
Tasks.
Custom anniversary dates.
Appraisals
Related contacts related to buyer and vendor.
Related Agents.
Listing documents (Authorities, section 32’s etc).
Communication history (doesn't include template preview, just basic history).
Notes.
Tasks.
Sales
Related contacts related to buyer and vendor.
Related Agents.
Inspection attendees' history.
Enquiry history.
Listing documents (Authorities, section 32’s etc).
Communication history (doesn't include template preview, just basic history) .
Notes.
Tasks.
Offers, Contracts and Commissions. * If commissions are not compatible, they won't get offers, contracts and commissions.
Leases
Related contacts related to tenant and landlord.
Related Agents.
Inspection attendees' history.
Enquiry history.
Listing documents (Authorities, section 32’s etc.)
Communication history (doesn't include template preview, just basic history).
Notes.
Tasks.
Offers & Contracts.
Commissions.
Prospect properties
Related contacts i.e., owners, past owners.
Related agents, i.e., prospecting agent.
Notes.
Tasks.
What's considered out of scope
With a data import, there will be circumstances in which the data is not a part of the agreed data services and is referred to as out of scope. The items below will be considered out of scope.
Document templates (email, letter, SMS etc.)
System & module configuration.
Sales Trust Module Balances.
Data & listing process
Below you will find a standard overview of the data and listing process:
Data Export - We will export data from your system into a CSV format.
Validation - This data will run through a validation process.
Data Import - This data will then get imported into your new system.
Match Listings - We will use an REAXML file to match listings from Real Estate to an Reapit Sales unique ID.
Appending - We will append images, headlines, descriptions and floor plans.