You are running into a data model mismatch between legacy and modern Power Pages.
The errors about missing adx_* tables (such as adx_website, adx_webpage) indicate that your environment is using the newer Power Pages architecture, while the solution you are deploying is built on the legacy portal data model.
What is happening
- The GitHub solution relies on legacy portal configuration stored in adx_* tables
- In modern Power Pages environments, that configuration model is no longer provisioned the same way
- Because those tables are not present, both:
- Configuration Migration Tool
- PAC CLI upload
fail when trying to load the data
Answers to your questions
1. Is the Volunteer Engagement repository still supported for new Power Pages environments?
Not for newly provisioned environments. It was built for the legacy portal model.
2. Is there a supported migration path from the legacy Standard Data Model (v1) to the Enhanced Data Model (v2)?
There is no direct automated migration for portal configuration. Most cases require partial or full rebuild.
3. Is there a v2 version of the Portal ConfigData available?
No official v2 version of that repository’s config is available.
Recommended approach
The most reliable path is:
- Create a new Power Pages site using the current studio experience
- Recreate or migrate only the required functionality manually
If you specifically need that solution, you would need an environment that still supports the legacy portal model, but this is becoming less common.
Key takeaway
This is not a deployment issue with your commands. It is a mismatch between a legacy portal solution and the current Power Pages platform model.
✅ If one of the responses here solved your issue, please mark it as Accepted so others facing the same problem can benefit as well.
👍 If this or any other reply here helped you, feel free to give it a Like. It helps others and is always appreciated.
