Skip to main content
Transaction Data Requirements | FUB Deals

Essential fields that must exist in your FUB Deals transactions to equip MaverickRE with the correct data to power your reports.

Sabrina Garrett avatar
Written by Sabrina Garrett
Updated yesterday

Overview

As a valued client of MaverickRE, we understand the importance of accurate and comprehensive reporting in your real estate business.

In this article, we will outline the essential fields that must exist in order for MaverickRE to pull in the correct data and provide you with accurate insights. To ensure seamless data integration from your transaction management system into your reports, it is crucial to have specific data present in every transaction. By ensuring that these essential fields exist in every transaction within your FUB Deals, you can leverage the full power of MaverickRE's reporting capabilities. Accurate and comprehensive data integration will provide you with valuable insights into your business performance, enabling you to make informed decisions and drive growth.

Remember, accurate data is the foundation of successful reporting, and MaverickRE is committed to providing you with the tools and support you need to thrive in the real estate industry!

What should I do if one of these fields doesn't exist in my deal cards?

Most of the fields listed below already exist on a transaction record, however, once your FUB data is imported into MaverickRE you will see some custom fields (listed below) that are populated in your deal cards.

Your MaverickRE Implementation Specialist will guide you through what is needed in the custom fields.

FUB Deal Transaction Requirements Breakdown

Each Deal in Follow Up Boss must contain the following data:

  • Price

  • Close Date

  • People - Lead in Follow Up Boss

  • Team - Agent or Agents associated with the deal

  • Custom Fields

    • Lead Source - Maverick

      • If the lead in FUB (buyer/seller) is associated under the People section, the transaction's source will automatically match the lead's source.

    • FUB Lead ID - Maverick

      • If the lead in FUB (buyer/seller) is associated under the People section, the FUB ID field does not need to be updated.

    • Acceptance Date - Maverick

    • Address - Maverick

    • Deal Type - Maverick (only used if you do not have separated pipelines)

      • Please note that we HIGHLY recommend using separate pipelines (Buyer\Seller).

*Important*

For required fields like FUB Lead ID and Address, these will automatically populate as long as:

  • The deal name (title of the deal) is set as the property address

  • The lead (buyer/seller) is properly associated with the deal under the People section on the deal card

Deal Type is only required if you do not have separate pipelines for Buyers and Sellers. This helps our system differentiate between listings and buyer deals. Your Implementation Specialist will guide you on whether this needs to be manually updated.

Important: To ensure an agent receives credit for a deal in MaverickRE, they must be listed as the Agent (Team) on the transaction (deal card).

The following fields are not required but are suggested to enhance the value of the insights that can be seen in MaverickRE if recorded:

  • Commission

  • Splits

  • Custom Fields

    • ISA Name - Maverick

    • Referral Commission - Maverick

Here is an example of a complete transaction in FUB Deals, including all required fields listed above.

Best Practices

Archiving Deals

When archiving a deal in FUB, the data will still sync into MaverickRE. These transactions will still show in your TMS related errors as well.

  • If your goal is to completely remove a deal, you should select the delete option instead of archiving.

  • If a deal fell through, it should be moved to a "Deal Lost" stage in its respective pipeline (Buyer or Seller) rather than being deleted.

    • If you do not have a "Deal Lost" stage in your pipelines, please create one and notify your CSM or MaverickRE support of the additions. This will allow us to map those stages on the backend to ensure that data is being pulled in properly.

Did this answer your question?