Joining the Agentbox Community | Migrating Data (X to AB)

 

 

In this user manual article, we will guide readers through how to understand your Agentbox's Data Import, such as data related to Contacts, Prospect Properties, Data Ownership and Post Import recommended tasks.  

 

 

Getting ready for a data migration 

 

  • Contact Ownerships: Our Agentbox data team will assign contacts to relevant staff based on your previous CRMs rules. Within your Agentbox Onboarding Walkthrough, our friendly team will discuss Agentbox's ownership configurations and options. A Master User of your Agentbox system can always change System Configuration, including Contact ownership rules, Primary Owner, Full Access or View Only.  

 

  • Contact classes and Custom Contact Classes: Depending on your scope of import, you may additionally have both Contact/ Custom Classes assigned to several of your contact database imports. Depending on your level of access within your system, you may like to review/ clean your existing categories created from the import.  

 

 

 

Contact Database Imports  

 

When a new Agentbox system launches, new Agentbox community members will be provided the opportunity to import contacts and discuss possible scenarios or issues raised. Please see below the 3 potential scenarios that will apply to contact imports:  

 

Scenario 1 - Duplicate Contacts Found: 

Agentbox stands out from other CRMs as we encourage a clean database policy. Due to this, we may see duplicate contact records when a client migrates to Agentbox from another CRM. Same last name, mobile and/or email, these contacts will be merged, and data appended. Any data that can't be appended is stored as a note.   

 

 

 

Scenario 2 - Conflicting contacts:  

There may be circumstances where a CRM may allow for conflicting data. Due to this, the process below will be followed in the scenario. 

  • Agentbox's Data Team will flag this and recognise.  

  • The Contact card often shares the same email and or mobile, and so the contacts will be imported, however it will remove the conflicting value (e.g., mobile and/or email address) and store this as a note, ensuring no data has been lost.  

  • Furthermore, these contacts will be assigned to the contact class, 'mobile/email removed'.  

By assigning this contact class, a new Agentbox user will be able to quickly locate, review and update contacts that fall within this category. Note: Master Users and those with the relevant permissions will be able to view the contact import.  

 

Scenario 3 - No Import Issues:  

A contact database will transition from their previous CRM to Agentbox's, and data will be found on a Contact Card. Click here to learn all about Contacts.  

 

 

Listings and Prospect Properties 

 

 

Listings 

Your listing import is based off what was advertised on Realestate.com.au only. This includes listing descriptions, headline, photos and the primary agent only.  

Private/ Internal information will not come across from the listing import. This includes Agency Agreements, Statement of Information, offers, commission values and contracts. 

 

Prospect Properties 

Prospect Properties data imports will have 2 potential scenarios, those that will be merged and those who won't be.  

 

Scenario 1 - Duplicates Found:  

Following Agentbox's clean database policy, duplicate properties will be merged, as this conflicting address will prevent the user from successfully reporting in Agentbox and limit the user's ability to use its intended features. This therefore will mean duplicate prospect properties will be merged into one, alongside a created note on the Prospect Property. 

 

Scenario 2 - No Duplicates Found:  

No duplicates will be found. Therefore, a new prospect property instance will be created successfully.  

 

 

Click the below links to access each relative user manual article:  

 

Was this information helpful?
light-box Image