How can I move imported questions into a question bank or import directly to a question bank?

First of all, I feel your pain. The "Question Bank vs. Test" silo is one of the most notorious limitations in Docebo, and 2,000 questions (with 10,000+ clicks) is a nightmare scenario for manual data entry.

As you've discovered, Docebo does not currently have a native bulk import feature (like CSV or GIFT) directly into the Central Question Bank, nor is there a public API endpoint to push questions there bypassing the course-level UI.

However, since you need this exact structure for your complex randomization (which the Question Bank handles beautifully once populated), here is a highly effective, modern workaround that many advanced admins are using: AI-Assisted GUI Automation.

Instead of manual clicking, you can use an AI (like ChatGPT or Claude) to write a simple browser automation script that mimics human clicks and does the copy-pasting for you while you grab a coffee.

The Automation Strategy

You can approach this in two ways depending on your technical comfort:

1. No-Code / Low-Code RPA (Power Automate Desktop or UiPath) If you are on Windows, you likely already have Power Automate Desktop installed. You can set up a flow that reads your questions and answers from an Excel file, opens your browser, and loops through the Docebo UI to click "New Question," paste the text, select the correct answer, and click "Save."

2. Browser Scripting via AI (Selenium or Playwright) If you have your original questions in a CSV or Excel file, you can literally ask ChatGPT to write a Python script for you.

• The Prompt: Explain to the AI what you need. For example: "Write a Python Selenium script that reads a CSV of questions and answers. It needs to navigate to [Your Docebo URL], log in, go to the Question Bank page, click the 'Add Question' button, paste the question, loop through the 4 answer fields, select the correct one, and save. Add a 3-second delay between actions."

• The AI will generate the exact code you need to run.

⚠️ Superadmin "Gotchas" to Watch Out For

If you go the automation route, keep these Docebo-specific quirks in mind:

• Pace Yourself (Crucial): Docebo has WAF (Web Application Firewall) rate limiting. If your script clicks and saves 100 questions a second, Docebo will think you are a bot launching a DDoS attack and temporarily block your IP. Make sure your script has built-in sleep or delays (e.g., 3–5 seconds between saves) to simulate human speed.

• Session Timeouts: Docebo will log you out after a period of inactivity. Make sure your script handles the login or runs in chunks of 200–300 questions at a time.

• Pre-build Your Folders: Manually create your "Area 1", "Area 2", etc., folders in the Question Bank before running the script. It's much easier to have the script target a specific folder than to have it create the folder structure dynamically.

The Alternative: Authoring Tools (SCORM)

If the automation route sounds too daunting, the other standard industry workaround is to abandon Docebo's native assessment engine for this specific use case. You can build the entire 2,000-question bank and the complex "pull 2 from Area 1, 4 from Area 2" logic inside an authoring tool like Articulate Storyline or Adobe Captivate. You then export it as a single SCORM package. Storyline handles massive randomized question banks much more elegantly than Docebo currently does.

Hang in there! The initial setup is tough, but your planned test structure sounds incredibly robust once it's up and running.