Power Platform Community Forum Thread Details

Hello,

I have quite a large solution that contains multiple tables and cloud flows etc that I would like to copy over to a different organization.

The solution currently has the prefix for one organization but I would like to update the prefix to the new organization but I am aware that I cannot modify the logical name of the table so there is no way to manually update this prefix.

What would be the best way to copy the tables to another org/environment but allowing the modification of table names/columns?

I was going to try and manually update the solution by exporting and unzipping then modifying the xml files but I am told this is not supported by Microsoft and they will not give me any support if I do it this way.

Does anyone have any advice?

Thanks in advance.

Categories:

Building Power Apps

You're correct that modifying the solution XML files directly is unsupported by Microsoft and can lead to unpredictable issues. However, there are supported ways to copy the tables, cloud flows, and other solution components to a different organization while updating the prefix.

Recommended Approach: Use a New Solution with the Correct Publisher Prefix

1. Create a New Solution in the Target Organization

In the target environment, create a new solution.
Assign a new publisher with the correct prefix for the new organization.

2. Export Your Existing Solution as Unmanaged

Go to Power Platform Admin Center > Solutions.
Select the existing solution.
Click Export > Choose Unmanaged (so you can modify it later).

3. Import the Solution into the New Environment

Go to the new environment and import the unmanaged solution.
This keeps your existing logical names but doesn’t change the prefix.

4. Manually Recreate Key Tables & Components

Since Dataverse tables' logical names cannot be changed, you must manually recreate the tables with the new prefix:

In the new solution, create new tables using the correct prefix.
Use Dataflows, Power Automate, or Excel Import to migrate data from old tables to new ones.

5. Migrate Cloud Flows and Update References

Open each Power Automate flow in the imported solution.
Update all table references to the newly created tables with the new prefix.
Save and test each flow.

6. Update Model-Driven Apps, Forms, and Views

Open your Model-Driven App (if applicable).
Update forms, views, and relationships to use the new tables.
Save and publish.

Alternative: Use Power Platform CLI to Automate the Process

If you’re comfortable with command-line tools, use the Power Platform CLI to extract and re-import the solution while modifying components:

Install Power Platform CLI (pac).
Run pac solution unpack to extract the solution.
Modify table schema manually (be cautious).
Use pac solution pack to repackage the solution.
Import into the target environment.

Key Considerations

Why can't you just use the original solution? Because the logical names retain the old prefix.
Can you automate table recreation? Yes, using Power Automate or Dataverse APIs.
Does this require manual effort? Yes, for table recreation and updating references.

Final Recommendation

For full supportability, follow these steps:

Create a new solution with the correct prefix.
Manually create new tables with the desired prefix.
Migrate data and update flows, apps, and references.

While editing XML directly is not supported, Power Platform CLI can offer more control if needed.

Community site session details

Copy solution tables to another environment

Recommended Approach: Use a New Solution with the Correct Publisher Prefix

1. Create a New Solution in the Target Organization

2. Export Your Existing Solution as Unmanaged

3. Import the Solution into the New Environment

4. Manually Recreate Key Tables & Components

5. Migrate Cloud Flows and Update References

6. Update Model-Driven Apps, Forms, and Views

Alternative: Use Power Platform CLI to Automate the Process

Key Considerations

Final Recommendation

Helpful resources

News and Announcements

Quick Links

Introducing the 2026 Season 1 community Super Users

Kudos to our 2025 Community Spotlight Honorees

Congratulations to the March Top 10 Community Leaders!

Leaderboard > Power Apps

Featured topics

Product updates

Community site session details

Copy solution tables to another environment

Recommended Approach: Use a New Solution with the Correct Publisher Prefix

1. Create a New Solution in the Target Organization

2. Export Your Existing Solution as Unmanaged

3. Import the Solution into the New Environment

4. Manually Recreate Key Tables & Components

5. Migrate Cloud Flows and Update References

6. Update Model-Driven Apps, Forms, and Views

Alternative: Use Power Platform CLI to Automate the Process

Key Considerations

Final Recommendation

Helpful resources

News and Announcements

Quick Links

Introducing the 2026 Season 1 community Super Users

Kudos to our 2025 Community Spotlight Honorees

Congratulations to the March Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > Power Apps

Featured topics

Product updates