Skip to main content

Navica MLS Implementation Instructions

Updated

How it works: 

Navica MLS uses our Reso Standard API to connect and pull changes from GrowthZone.

 

PROJECT KICKOFF

Overview: 

The customer will need to work with Navica to obtain a RETS Feed contract, to provide to the Integration Specialist. Once obtained, Integration specialist pulls data. Testing is done in Stagin. 

 

Ticketing Process for RE Integrations (Review the below and we'll remove the red notation)

  • When communicating with customer and Navica, the Integration Specialist will CC platformintegrations@growthzone.com email to create a Navica- (Tenant  Name) ticket for project visibility. That ticket will then be related to the main Migration ticket.
  • All communication with the vendor, for the project, will be tracked in this related ticket. All project movement, communication between GZ Teams, updates, date files, and meeting dates will still be placed in a private note in the main Migration ticket for the Onboarder and Migrations team. 
  • The purpose of the related Navica- (Tenant Name) ticket is to allow visibility on the vendor communications for all RE Integrations staff. The related Navica- (Tenant Name) ticket will remain In Progress until the full integration is turned on and completed. The RE Integration point of contact for the project will be the Assignee on the related Navica- (Tenant Name).

 

Data Process: 

  • Customer will need to work with their support rep at Navica to obtain a RETS Feed contract. This will need to be signed by the customer before GZ can have access to their RETS feed.

  • GZ Onboarder should ask customer about Lockbox integration – as Navica does have Supra integrations (maybe other vendors too). So this might be a case where if the customer wants to keep their Supra integration feeding off of their MLS data, they can. OR if they want everything in GZ we could setup Supra for them.

  • When Onboarder puts in the request for a GZ Staging environment – also send email to Steven Potts, spotts@navicamls.net, to give him a heads up that he will need to spin up a Navica testing environment/replica database for this customer.

    • That said, it typically only would take him a couple days to get a replica database functioning to test with.

 

Customer requests RETS feed info from Navica. We will pull down the data from RETS to populate their tenant in GrowthZone.

 

 

Outlined process for other integrations that may be occuring simutaneously: 

M1 (if applicable) - https://helpdesk.growthzone.com/staff/kb/articles/2395-nrds-implementation-instructions

 

Lockbox (if applicable) -

Sentrilock https://helpdesk.growthzone.com/staff/kb/articles/2392-sentrilock-implementation-instructions;

SUPRA https://helpdesk.growthzone.com/staff/kb/articles/2391-supra-implementation-instructions

 

STAGING| DATA REVIEW

 

  • Once the data has been pulled from FLEX and all other integrations, the Integration Specialist will create a staging database.
  • Verify the Import Feature Settings are on. Setup -> Import Features
  • Verify in the Setup -> Real Estate Integrations -> MLS Tab  that FLEX is selected as the MLS. 
  • Once all data sources are obtained, and the Staging Database is created, the Integration Specialist will move the ticket to In Review for the Onboarder to move to Migrations when ready. 

Once the Staging data has been imported by Migrations, it should be reviewed by Onboarding in conjunction with Platform Integrations and the Customer to ensure that the data was being imported correctly.  

Double check that the GrowthZone Real Estate API has been setup by Integration Specialist
Go to Setup>Applications>API Key Permissions ***If this is not a visible option in Setup, then the API module needs to be added via tenant settings.

 

Add API Key for NavicaMLS:
Go to Setup>Applications>API Key Permissions, and add “NavicaMLS”

 

 

 

Set up the Real Estate Edition Settings for the tenant:
Setup > Integrations > Real Estate Edition Settings 

  1. Set the MLS Type to “Standard”

  2. Set Section Title to “Navica MLS”

  3. Select sync to MLS

  4. Set the MLS Go Live time as now.

  5. Fill out the Affiliate ID - (< more information coming on this from product)

  6. NOTE: Do NOT utilize the MLS ID Generators (neither the Office or the Agent one)

    1. With Navica selected, they will instead see a “Get MLS ID” button automatically upon this being setup, on both the Agent and Office MLS ID sections. This is the method they should utilize, unless they are confident in the existing MLS ID.

  7. Fill out the MLS Mappings Section

Select “Save” when you are done.
 

Force Kafka:

Go to Setup>GrowthZone Staff Only Tools>KafkaUtilities>Force Changed Contact Kafka
 

Testing with Navica & Customer. Onboarder should reach out to Steven Potts, letting them know that the GZ staging environment is ready, and testing can begin with the Navica testing environment/replica database.

  1. Testing STEPS:
    - Add a New Office - sync it
    - Add a New Agent - sync it
    - Edit an existing Office
    - Edit an existing Agent

  2. NOTE - Changes will be sent to Navica and communication will need to be had with Steven OR Navica support rep, to understand if changes are coming through correctly.

 

GO LIVE 

Coordinate Go Live date & time with customer and Steven Potts (from Navica). Cannot go live on Fridays! 

  • Once Conversions has completed their task, complete the steps 1 - 4 (as noted above), but this time in their production environment, expect for:

    • When checking the “Sync to MLS” flag, set the go live date & time. Remember to set the time for at least 2hrs from the time you are completing this to allow for all contacts to get to IIT. For example, if it is 8:00 AM set the go live time to 10:00 AM. 

  • Then, go to Setup>GrowthZone Staff Only Tools>Kafka Utilities>Force Changed Contact Kafka