We’ve added two of the most requested models to the Partner Data Warehouse:

charge_consumption

• Provides detailed kilowatt-hour (kWh) time-series consumption data for individual charges on Monta-connected (OCPP) charge points—enabling deeper energy usage analysis.

reports

• Captures issues, feedback, and incidents related to charge points, charges, or operators. This includes user-submitted reports, system-generated alerts, and Zendesk support tickets.

These models are live now and unlock better operational insights and energy analytics directly from your DWH.

Release ETA Week 3, 2026

What’s New We’re updating the FUTURE__charge_points table in Week 3, 2026. This update introduces key improvements to data quality and model consistency compared to the legacy charge_points model.

Here’s what’s changing:

1. The new version passes our latest and more stringent data quality tests, ensuring higher accuracy and reliability.
2. Duplicate charge points are now removed when multiple sponsorship relationships exist for the same charge point. All sponsorship relationships can now be found in the FUTURE__sponsored_charge_points model.
3. Columns related to sponsored charge points have been removed and are available in the FUTURE__sponsored_charge_points model instead.
4. Filtering logic remains unchanged: the model includes both charge points operated by a team under your operator ID and charge points sponsored by a team under your operator ID.

Additional documentation and details about the updated model will be released in early 2026 ahead of this release.

Alongside this release, we’ve introduced a new Migration Data Quality Tracking page in our documentation. This status page is live now.

You can use this page to track the readiness of all FUTURE tables and see whether we’re investigating any known data concerns. We’ll keep this page regularly updated throughout the migration.

Why It Matters The ongoing Partner Data Warehouse migration focuses on improving data quality and consistency, ensuring the data can be trusted for analysis and reporting across all models.

Related Links & Resources

Migration Data Quality Tracking Page

Release ETA: Live now

What’s New

We’ve fixed a bug in the FUTURE__charges table of the Partner Data Warehouse.

Previously, the avg_co2_kwh column was showing total CO₂ emissions per charge instead of average emissions per kWh.

The update includes:

✅ Corrected avg_co2_kwh: now shows average CO₂ emissions (in kg) per kWh for the energy delivered.

✅ **Added new **co2 column: reports total CO₂ emissions (in kg) produced for the given charge. (co2 column previously existed in the pre-migration table)

Why It Matters

This update enables more accurate and granular insights into the CO₂ impact of charging sessions, supporting better ESG reporting and environmental analysis.

Release ETA

Week 50, 2025

Alignment with Partner API

We’re completing the migration of all Partner Data Warehouse models. With this release, all remaining models are now aligned and expanded to match the Partner API, ensuring full consistency across both systems. The new FUTURE__ models match or exceed the rows and columns available in Partner API

Aligned and Expanded Models (FUTURE__ tables added alongside existing models)

• FUTURE__application_users
• FUTURE__applications
• FUTURE__charge_keys
• FUTURE__charge_member_costs
• FUTURE__charge_point_sites
• FUTURE__operators
• FUTURE__plans
• FUTURE__subscription_purchases
• FUTURE__subscriptions
• FUTURE__tariff_period_groups
• FUTURE__tariff_prices
• FUTURE__tariff_recurring_periods
• FUTURE__team_members
• FUTURE__team_price_groups
• FUTURE___transactions
• FUTURE___users

New Models

In addition, two new models have been introduced to enhance data modeling and analysis:

• FUTURE__team_owners - Provides clearer visibility into user roles in the users table. The users table includes data on users who are application users, team members, or team owners. With the new table you can clearly link each user ID to their corresponding role(s): team member, team owner, or application user.
• FUTURE__tariffs - Includes base tariff data to enrich existing tariff-related tables.

Why It Matters

This release completes the alignment between the Partner Data Warehouse and the Partner API. It provides consistent, reliable data across systems, simplifying integration and enabling more accurate reporting and analysis.

🛠 Alignment with Partner API

See migration details here:

FUTURE__ tables included in this release

• FUTURE__charge_points
• FUTURE__teams
• FUTURE__charges
• FUTURE__charge_pricings (note table name change from charges__charge_pricings)
• FUTURE__charge_configs (note table name change from charges__charges_config)
• FUTURE__sponsored_charge_points
• FUTURE__failed_charges_info
• FUTURE__charge_pricing_breakdowns
• FUTURE__charge_pricing_breakdown_specifications

✨ New Tables Added

• vehicles

  • vehicles integrated by operator’s teams or users
  • matches vehicles endpoint in Partner API

• Data Enrichment Tables

  The tables below are added to enable futhre data enrichment. These are are not filtered to partner specific context

  • charge_point_models
  • countries
  • country_areas
  • currencies

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

DEPRECATED and FUTURE tables removed

As the final step in the migration to the new Charges tables, the tables labeled DEPRECATED and FUTURE were removed.

fully_charged_at added to charges

fully_charged_attimestamp is now available in the chargestable.

Now live:

• charges tables were replaced with the new data from FUTURE__tables. Old data can still be found in DEPRECATED__charges until 15. September.
• applications table

Happy summer. This week we are releasing small changes to polish some recent releases.

FUTURE__charges

New columns:

• completed_at
• application_id
• vehicle_id
• roaming_provider
• is_roaming_charge

In late May 2025 we began the process of migrating the charges table to a new setup. (Read more here We have decided to extend the migration timeline to allow for more time to prepare for the coming breaking changes.

Already live:

• The new charges , charge_pricings, and charges_config tables are already live, they have the FUTURE__ preposition.
• Documentation for these changes is already live

Next steps

2025-08-15

• Existing charges table will gain the DEPRECATED__ preposition and become DEPRECATED__charges table. No other changes will be made to the table and the data in this table will continue to be updated.
• The new tables will be available both with and without the FUTURE__ preposition allowing preparing your codebase for the future stable state.

2025-09-15:

• Tables with the DEPRECATED__ and FUTURE__ preposition are removed