Skip to main content

MLS Common Backend Conversion

jperez jperez

The MLS Common Backend is a new, unified system that standardizes how listings are entered, validated, searched, and distributed across the MLS.

Why you’re seeing this: This change replaces multiple legacy backend systems that may have behaved differently behind the scenes, creating one shared foundation for more consistent results.

Why This Change Is Happening

  • Eliminates inconsistencies caused by multiple backend systems
  • Reduces technical risk and long-term infrastructure costs
  • Creates a single source of truth for MLS rules and validations
  • Supports faster, consistent response to industry and policy changes

How Members Benefit

  • One standardized Add/Edit experience across desktop, tablet, and mobile
  • Auto-population of listing data from trusted sources (such as public records)
  • AI-assisted tools to help write remarks and analyze photos for listing data
  • Faster listing entry with fewer errors and corrections
Good news: Saved searches and subscriptions are expected to auto-convert, but we recommend reviewing them after the transition.

RESO Compliance (Why It Matters)

The Common Backend is built on RESO standards, the universal industry standard for MLS data. This supports:

  • Consistent listing data formatting across vendors and brokers
  • Fewer custom workarounds and data mismatches
  • Faster onboarding of new products and integrations
  • More future-proof tools and data connections

Items That Will NOT Convert Automatically

Some customized or legacy items cannot be automatically converted due to system differences. Plan to recreate or review these items after the transition.

Heads up: If you rely on custom views, exports, reports, or market areas, set aside time to rebuild them after the change.

Matrix – Items Not Converting

  • Email history
  • CMAs
  • Custom exports
  • Custom one-line displays
  • Saved Hotsheets
  • Saved MarketWatch
  • Saved Stats
  • Home page widget information

FlexMLS – Items Not Converting

  • Incomplete (partial) listings
  • General preference selections
  • Custom quick search templates
  • Custom views
  • Custom exports
  • Saved sorts
  • Custom reports / business cards
  • Market areas

What to Expect During the Transition

  • A parallel system period to minimize disruption
  • The new backend will be used for Add/Edit
  • The existing system may still be used initially for search and subscriptions
Important: After the transition, review your auto-converted saved searches/subscriptions to confirm they still match your intended criteria.

What Do I Need To Do? (Quick Checklist)

  • Finish or remove any incomplete/partial listings (Flex users)
  • Export or document key custom settings you want to recreate (views, exports, reports, templates)
  • Take screenshots of your most-used setups (quick searches, views, widgets, market areas)
  • Make a short list of saved searches/subscriptions you rely on most
  • Plan a review session after conversion to confirm searches/subscriptions and rebuild custom items
Tip: If you’re not sure whether something is “custom,” assume it is and document it before the cutover.

FAQs

Will I lose my listings?

No. Your listings remain in the MLS. The change impacts the backend system that controls how listings are processed and validated.

Will my saved searches and subscriptions still work?

They are expected to auto-convert, but you should review them afterward to confirm filters and results still match what you intended.

What should I review first after the transition?

Start with the items you rely on daily: your saved searches, subscriptions, and any custom views/exports you use for clients or internal tracking.

Why are some things not converting?

Some items are built differently in legacy systems and can’t be automatically migrated. These are usually customized tools like views, exports, reports, and certain saved workflows.

I use custom views/exports constantly. What should I do now?

Before cutover, document what you use (screenshots and notes). After conversion, you’ll be able to recreate them.

What happens to my CMAs and email history (Matrix users)?

CMAs and email history are listed as items that do not automatically convert. If you need to retain details, document them before the transition.

Will Add/Edit look different?

You should see a more standardized Add/Edit experience across devices. The goal is fewer errors, more consistent validations, and faster entry.

Does this affect my third-party apps and integrations?

The Common Backend supports more standardized data (RESO) and secure API-based transmission, which typically improves compatibility over time. Some vendors may release updates as the transition progresses.

Who do I contact if something looks wrong after the switch?

Contact the MLS Support Team with specifics (listing number, screenshots, and the steps you took) so we can troubleshoot quickly.

Was this article helpful?
0 out of 0 found this helpful