Quick solution but comes with a bug

Hi, Thank you so much for this app as it helps alot when it comes to the quick migration. But one thing which made a mess is that it creating special characters after the import of the articles in the text which may need to be removed manually as the file tool exports is .kt file which is not editable. Any suggestions to this will be appreciated. thanks

Hi Hamza, Thank you for your feedback. Could you please send more details about the issue to the support email? You can find it on the AppExchange listing under More Details → Need Help? → Email. We’ll have a look and do our best to resolve it.

Thank you!! No more Data Loader Wrangling

This tool has completely transformed the way our organisation works with Salesforce. Anyone who has spent time in the Salesforce ecosystem knows how painful it can be to seed Sandboxes with Knowledge Articles. Historically, this has been a persistent pain point for us—time‑consuming, error‑prone, and a major blocker for our development teams when spinning up new environments or testing changes confidently. This app stands out because of its elegance and simplicity. In just a few clicks, we were able to move Knowledge Articles seamlessly from Production into a newly created Sandbox, with all relevant metadata fully intact. Even better, data categories were transferred flawlessly, something that is normally forgotten. What used to take hours of manual effort is now fast, reliable, and repeatable. The impact on our Dev teams has been huge—they can focus on building and testing instead of wrestling with environment setup. This tool has quickly become an essential part of our Salesforce workflow, and I honestly can’t imagine going back to the old way of doing things. Highly recommended for any Salesforce team that works heavily with Knowledge and Sandboxes.

Files / Images not migrating, multiple issues are present

I attempted to extract a Knowledge Article (KA) from one Salesforce org and import it into another. The article contained both image and text file attachments and included multiple versions. After completing the import, I observed several issues in the target org: 1. Image and text file attachments are not visible in the imported Knowledge Article. 2. Last Modified By, Assigned To, Article Created By, and Owner fields were overwritten with my user information as part of the upload process. 3. Comments and associated files are not displayed in the target org. 4. Only a single version of the article is present—multiple versions from the source org were not migrated. 5. Approval history is missing from the imported article.

Hi Ranjit, Knowledge Loader shows exactly the same articles that are available in Salesforce list views. The app itself does not calculate or display article counts - just like list views - so it’s unclear how the comparison was performed. If there are specific articles that you can see in a list view but not in Knowledge Loader, please contact us using the support email listed on the AppExchange page, and we’ll be happy to investigate.

I faced another challenge in Knowledge loader app. From Backend I can find the article count for each article status . But from knowledge loader app , when I am trying to extract , I can see less number of articles. For example : Draft - 562 records ; but Knowledge Loader gives 70 records Online - 1730 records but knowledge loader gives 1120 records Archived - 4505 records but Knowledge loader gives 3520 records only Can anyone tell me how knowledge loader app gives / shows correct number of knowledge articles in export screen?

Hi Ranjit, thank you for taking the time to share your feedback. I’d like to clarify how the app currently works and what is within its supported scope: 1. Images & files The app migrates images that are embedded directly inside Knowledge Article rich text fields. Legacy file attachments or separate Salesforce Files are not migrated. If an image is embedded in the article body and did not migrate, please contact us via the email in the listing and we’ll be happy to assist. Otherwise, this falls outside the app’s current capabilities. 2. Audit fields (Last Modified By, Created By, Owner, Assigned To) This behavior is intentional and by design. During migration, these fields are set to the running user to preserve audit integrity and clearly indicate who performed the import. 3. Comments and associated files Migration of comments and their related files is not part of the app’s capabilities at this time. 4. Multiple article versions The app imports the latest published version only. If you have a business case that requires migrating historical versions, please share it with us and we’ll consider it for a future release. 5. Approval history Approval history migration is not part of the app’s capabilities at this time. We continuously aim to be transparent about what the app does and does not support, and we appreciate feedback that helps shape future improvements.

Help & Support

Elevate Your Agents with AgentExchange Solutions

Have Questions?

Knowledge Loader

Watch Video

Showing 3 of 3 Reviews