Resolving Flow Import Error Due to SharePoint Connector Reference
Hi everyone,
Sharing a quick POSSIBLE solution for an issue you might encounter when importing a Power Automate flow (ZIP package) into your environment.
🚨 Problem
When attempting to import a packaged flow, you may see an error similar to:
Import failed for one more package resources.
This typically happens because the flow is still referencing a SharePoint site URL from the source environment (e.g., a different tenant or subdomain). Some time you will get a "Save as a new flow" link where you will be taken into editing mode of flow in draft mode and able to continue. But sometime that link does not exists.
✅ Root Cause
The flow definition includes hardcoded references to a SharePoint domain such as:
xyz.sharepoint.com
If your organization uses a different SharePoint subdomain (e.g., abc.sharepoint.com), the import will fail because the connector cannot resolve or authenticate against the original URL.
🛠️ Solution
You can resolve this by updating the flow definition before importing:
Step-by-step:
- Unzip the flow package (.zip file)
Extract the contents to a local folder. - Locate
definition.json
This file contains the flow’s configuration and connector references. - Open the file in a text editor
Use Notepad, Notepad++, or similar. - Find and replace the SharePoint domain
- xyz.sharepoint.com
- abc.sharepoint.com
- Save the file
- Repackage the zip file
- Ensure the structure remains unchanged when zipping it back up.
- Re-import the flow The import should now complete successfully.
💡 Tips
- Make sure all occurrences of the old domain are replaced.
- Be careful not to alter the JSON structure.
- If multiple connectors are used, double-check for additional environment-specific URLs.
Hope this helps anyone running into this issue! Let me know if you’ve found other variations or edge cases.
Answers
-
This is super helpful Alex, thanks for sharing! I've been able to get around this in the past by adding the Flow into a Solution and using Environment variables but the use of Solutions has also created other challenges in some situations so will definitely be giving this a try!
2
Categories
- All Categories
- 7 Blackbaud Agents for Good™
- New Raiser's Edge NXT Community
- 7 Blackbaud Community Help
- 214 bbcon®
- 1.4K Blackbaud Altru®
- 407 Blackbaud Award Management™ and Blackbaud Stewardship Management™
- 1.2K Blackbaud CRM™ and Blackbaud Internet Solutions™
- 16 donorCentrics®
- 361 Blackbaud eTapestry®
- 2.6K Blackbaud Financial Edge NXT®
- 669 Blackbaud Grantmaking™
- 591 Blackbaud Education Management Solutions for Higher Education
- 3.3K Blackbaud Education Management Solutions for K-12 Schools
- 950 Blackbaud Luminate Online® and Blackbaud TeamRaiser®
- 85 JustGiving® from Blackbaud®
- 6.9K Blackbaud Raiser's Edge NXT®
- 3.9K SKY Developer
- 252 ResearchPoint™
- 121 Blackbaud Tuition Management™
- 165 Organizational Best Practices
- 245 Member Lounge (Just for Fun)
- 38 Blackbaud Community Challenges
- 37 PowerUp Challenges
- 3 (Closed) PowerUp Challenge: Grid View Batch
- 3 (Closed) PowerUp Challenge: Chat for Blackbaud AI
- 3 (Closed) PowerUp Challenge: Data Health
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Product Update Briefing
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Standard Reports+
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Email Marketing
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Gift Management
- 4 (Closed) Raiser's Edge NXT PowerUp Challenge: Event Management
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Home Page
- 4 (Closed) Raiser's Edge NXT PowerUp Challenge: Standard Reports
- 4 (Closed) Raiser's Edge NXT PowerUp Challenge: Query
- 813 Community News
- 3K Jobs Board
- 57 Blackbaud SKY® Reporting Announcements
- 47 Blackbaud CRM Higher Ed Product Advisory Group (HE PAG)
- 19 Blackbaud CRM Product Advisory Group (BBCRM PAG)

