HomeGuidesChangelog
Changelog
Monta.com
Start typing to search…
Back to All
Improved

🚀 Partner Data Warehouse Aligns with Partner API

October 23rd, 2025

Launch of Migration

We’re aligning Partner Data Warehouse with Partner API!

Starting soon, new data models will expand coverage to match (or even exceed) the Partner API — a major step requested by many of our partners.

🗓 Release Timeline

  • Week 45 (First full week of November 2025): ✅ No breaking changes:
    • We release first migrated tables with the FUTURE__ prefix.
  • End of 2025: ✅ No breaking changes:
    • All FUTURE__ tables are released.
  • Week 15 (First full week of April 2026): ⚠️ First breaking change:
    • FUTURE__ tables mirrored to main tables.
    • old tables added the DEPRECATED__ prefix.
  • Week 28 (First full week of July 2026): ⚠️ Second breaking change
    • removal of all FUTURE__ and DEPRECATED__ tables.

🔄 What’s Changing

  • Expanded data coverage: Partner Data Warehouse will now match the Partner API.
  • More and improved fields: Some tables will gain new columns.
  • Standardized IDs:
    • Primary keys → id
    • Foreign keys → {table_name_singular}_id (e.g. team_id links to id in teams)

All new models will contain the same or more data than your current ones.

⚙️ How Migration Works

  1. New tables released (✅ No breaking changes)
    1. Week 45 and finished by Year End 2025
    2. new tables appear with a FUTURE__ prefix.
  2. Migration period (3 months)
    1. Migrate your queries and reports to FUTURE__ tables by Week 15 (first full week of April 2026).
  3. Mirroring & renaming ( ⚠️ Breaking change).
    1. Week 15 - first full week of April - 2026
    2. main tables aligned with FUTURE__ (FUTURE__ tables continue to be available)
    3. old tables renamed DEPRECATED__
  4. Cleanup period (3 months)
    1. Remove FUTURE__ prefixes in your code by Week 28 (first full week in July 2026).
  5. Final removal ( ⚠️ Breaking change)
    1. Week 28 (First full week of July 2026).
    2. All FUTURE__ and DEPRECATED__ tables deleted

💡 Why It Matters

This migration ensures:

  • Full alignment between Partner Data Warehouse and Partner API.
  • Consistent identifiers and easier data joins.
  • Improved data quality and coverage across all tables.
  • Clear, updated documentation before the final rollout
  • Thorough data quality testing implemented on all new tables

📢 What You Can Do Now

  • Prepare to migrate to FUTURE__ tables during the migration period
  • Start reviewing your existing queries and reports to pan out what work is needed
  • Watch for upcoming announcements of table and documentation releases