Forum Discussion
Changing Data Centre from US to EU
Even when you contact Articulate directly, they ignore you. I feel like they don't care AT ALL. For them it's pretty convenient to have users having to pay twice for the same license just to be able to do their job. ðŸ˜
Hi Kelly​,
I'm sorry to hear that this has been your experience when contacting Articulate Support!
Checking the case history associated with your Articulate ID, I'm not seeing any requests that went unanswered. If you're comfortable sharing more details on a specific instance, I'm happy to take a closer look. Please let us know!
Hi StevenBenassi​,
To clarify: I'm not saying my support cases went unanswered in the sense that nobody replied. I'm saying the actual issue I raised was never addressed.
When I contacted support, I received two responses. The first explained why Articulate has separate data centers, which wasn't my question. The second told me I could share the published output of my Rise courses, which also wasn't what I asked for. What I asked for was a solution that allows users on different data centers to collaborate on Rise courses.
None of that was ever addressed. That's what I mean when I say Articulate is ignoring customers on this issue. A reply is not the same as an answer.
My support case was eventually closed with a feature request, for something that, in my view, is a basic expectation of a professional collaboration tool, not a feature request.
There are multiple users on this forum who run into the same wall. And now, according to another user in this thread, Articulate has confirmed in writing that cross-data-center collaboration is not on the roadmap? If that's true, it would be helpful to say so clearly and officially, so that affected users can make informed decisions about their tooling. The continued silence on this issue while so many users, who are paying premium license fees, are affected doesn't exactly suggest that customer needs are a priority for Articulate. So yes, users do feel ignored.
Hey Kelly​,
I appreciate you following up and sharing the candid feedback.
This is a request we've heard from other users, and I completely understand the value it would bring. I can confirm that each voice is logged, reviewed, and contributes to how our product team understands customer needs and prioritizes their work. The volume of requests matters, but so does the context around how the absence of this feature impacts real workflows.
We always want our users to feel heard while also offering complete transparency. Enabling seamless collaboration across data centers requires significant changes to how data is stored, accessed, and synchronized across regions. Also, with careful consideration of performance, reliability, and data governance. That doesn’t make these requests any less valid. It just means the path to solving it is more involved, and must be weighed alongside other improvements we’re making across the Articulate 360 platform.
While I don't have any updates to share right now, conversations like these do influence how our teams evaluate problems and potential solutions over time.
Please let me know if I can help with anything else!
Hi StevenBenassi​,
Thank you for your reply. However, I don’t feel like this really helps. You’re still not addressing the actual request.
You describe the complexity of synchronising data across data centers, which nobody asks for. An export-import feature would do the work, and would work completely differently: you export a Rise course from one environment, import it into another, and from that point on the two copies are independent. No synchronisation, no cross-region data access, no shared storage. The data stays exactly where it is. Your response in no way explains why a standalone export-import feature for Rise isn’t on the roadmap. Although your reply sounds thorough, it doesn’t actually address what global users are asking for: a simple export-import feature.
I recently imported a SCORM zip file of a Rise course into Mindsmith. The result was impressive. If a smaller competitor can already do this, it's hard to see why Articulate hasn't prioritised this yet.