🛠 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

• This week we are releasing many overdue items from the promised roadmap.
• Many of the items were in fact already released, but now we are announcing them. Documentation is also being updated to reflect the changes.

The updates now live are:

April

• New Tables
  • plans (documentation is being updated)
• Columns to Existing Tables
  • transactions
    • note
    • to_operator_name
    • from_operator_name
    • to_wallet_vat_number
    • from_wallet_vat_number
    • exchange_rate (can be calculated from current to_eur and from_eur conversion rates)
  • teams
    • partnerExternalId
    • type
  • charge_keys
    • team_id
    • user_id
  • charge_pricing_breakdown
    • operator_id
  • subscriptions
    • serviceConfig
  • charge_points
    • partnerExternalId
    • maxKw
    • isActive (Depends on whether state in DWH behaves like the API — a disabled CP might still show an "available" state)
    • costGroupId
    • sponsorPriceGroupId
    • sponsorChargePointId reference
  • charge_point_sites
    • partnerExternalId

May

• Columns to Existing Tables
  • transactions
    • metadata

As promised here the new future__charges tables were released today to all partners

Aircall Calls table released (for specific customers)

Specific customers with custom call center numbers can now analyze their call center activity. This table is manually turned on for customers who request it and who have custom call center numbers in our system

Table documentation for future__charges(and subtables) now available

As outlines in the 2025+05+28 change log, the update to our chargestable is coming. As promised the documentation is now live for the new future__charges, future__charges__charge_pricings and future__charges__charges_configtables.

Recent changes to transactions

(2025-05-28) We recently made 2 changes to the transactions table. This links to deeper re-engineering work at Monta, but also to efforts to make data in the Partner Data Warehouse align more cleanly with the raw data one can query from the API or see in the Hub.

• column transaction_idis now id
• columns to_currency_rate_eurand from_currency_rate_eur were removed.

Please contact us, if these changes are causing issues in your setup.

Coming changes to charges table -- June to August 2025

Overview of changes and motivation

(2025-05-28) We are redesigning the way our charges table is created. This links to deeper re-engineering work at Monta, but also to efforts to make data in the Partner Data Warehouse align more cleanly with the raw data one can query from the API or see in the Hub.

With these changes, we will replace the charges table and add two new tables charge_pricings and charges_config. Some columns currently in charges will in the future exist in the new tables. The three tables can be joined using charge_id.

COMING IN WEEK 23: Schema pages for the coming tables

Timing of the changes

• before 2025-06-15: New charges, charge_pricings, and charges_configtable will appear with the FUTURE__ preposition. No changes will be made to the existing table.
• 2025-07-15: Existing charges table will be renamed with DEPRECATED__ preposition. New tables will be available both with and without the FUTURE__ preposition allowing preparing your codebase for the future stable state.
• 2025-08-15: Tables with the DEPRECATED__ and FUTURE__ prepositions are dropped

Some highlighted changes in the charges table

• is_deleted_charge column is removed.
  • This column is always 0 in the current table, so no data is lost
• avg_renewable column is removed
• start_source, payment_method , payment_method_type and state columns have same universe of values but the values have different format
  • values are in upper case
  • values use _ separator instead of -