--- title: "Cornerstone Single Architecture Migration: A Quick Move or a Chance to Rethink? | Octily" source: https://octily.com/insights/cornerstone-single-architecture-migration/ description: "Moving to Cornerstone Single Architecture? See what L&D and HR teams should review before migrating, from manual work and learner experience to reporting, customizations and rollout planning." --- # Moving to Cornerstone Single Architecture: A quick move, or a chance to rethink? ![Simen-Ling La](https://ebnnmeydktscnefergjm.supabase.co/storage/v1/render/image/public/client-logos/team/simen-ling-la.png?width=168&quality=70&resize=contain) Written by Simen-Ling La Publication date October 21, 2026 Categories Consulting Insights Reading time 9 min read 9 min read 0% 9 min We’re talking about Single Architecture a lot at the moment. Quite a few organizations that use Cornerstone are preparing for the move or are already right in the middle of it, and understandably a lot of the focus is on getting there as smoothly and efficiently as possible. It’s something we’re working on with organizations too. At Octily, we help organizations [**migrate and optimize their Cornerstone environments for Single Architecture**](https://octily.com/consulting/), looking at the existing setup, what needs to move or change and where things can be simplified or improved along the way. There’s nothing wrong with going for a fast migration. If your current Cornerstone setup works well, keeping the project focused and getting everything you need working in the new setup might be exactly the right approach. But your Cornerstone environment may have been set up years ago. Since then, your organization has changed, L&D and HR have changed and what is possible has changed quite a bit too. So if you’re already taking a close look at Cornerstone, it’s worth using the opportunity to look at more than what needs to stay the same. And some things may need to be set up again anyway. Not every page, setting or customization will necessarily move across one-to-one. **If you have to rebuild something, don’t automatically rebuild the old version. Ask whether it’s still the version you want.** You don’t have to turn the migration into a huge transformation project, and you certainly don't have to do everything at once. Sometimes it’s simply about asking the right questions now, deciding what is worth improving and building those things into a rollout plan for later. ### Is the experience you have today still the experience you want? It’s easy to approach a migration by looking at what you have today and making sure it still works afterwards. But something working technically doesn’t necessarily mean it’s working well for the people using it. Look at your Cornerstone environment as an employee for a moment. Can you quickly find what you need? Does your Welcome Page still help people get somewhere, or has it gradually filled up with links and information? Do employees in completely different roles, countries or departments really need the same starting point? Then look at it from the L&D side. How easy is it to keep those pages relevant? Can your team make changes when they need to, or does every update become a development request? And don’t just look at what people can see. Take stock of what sits behind the experience too. Custom pages, integrations, customizations and even the clever workarounds your team has relied on for years are worth reviewing. Some may carry over with relatively little work, while others may need adjusting or rebuilding as the platform underneath them changes. These are areas where customization still has a big role to play. Custom pages can create more useful experiences for different parts of the organization, and with the [**Octily Content Editor (OCE)**](https://octily.com/products/octily-content-editor/), L&D and HR can manage the content, languages and personalization afterwards without needing development for every change. It doesn't mean you need to redesign everything. It means this is a good time to check whether what you already have still fits, and whether everything you have today is actually worth carrying forward. Just ask yourself: **If we were setting up our Cornerstone experience today, would we still build it this way?** ### What is L&D or HR still doing manually? ![Illustration: manual Cornerstone tasks taking 4 hours every week versus 30 minutes instead](https://ebnnmeydktscnefergjm.supabase.co/storage/v1/object/public/insights-images/articles%2Fcornerstone-single-architecture-save-time.webp) Some of the best opportunities to improve your Cornerstone setup probably won't be on the migration plan at all. They're the Excel file someone updates every Monday. The report managers keep asking L&D to send them. The process that takes six steps because that's simply how it has always been done. Or information that technically exists in Cornerstone, but is too difficult for the people who need it to get to themselves. Those small tasks add up. And unlike some of the bigger changes you might be considering, they can be relatively easy to put a value against. If a process takes your L&D team four hours every week, what would it mean if you could reduce that to 30 minutes? If managers could get the information themselves, how many requests would that take away from your team? This is where it can be useful to look at the problem before deciding on the answer. Sometimes a change to the existing setup is enough. Sometimes a very specific piece of functionality is missing. That’s how we approach [**MicroApps**](https://octily.com/products/cornerstone-microapps/). They don't try to change all of Cornerstone. They add something specific where an organization needs it. [**Team Training Progress**](https://octily.com/products/microapps/team-training-progress/), for example, gives managers a much easier way to see training progress across their reporting structure, including assigned, completed and overdue training, without relying on L&D to pull that information together for them. There will be completely different examples in every organization. Start finding them and you can also start putting numbers against them. That makes it much easier to decide which improvements are actually worth prioritizing in your rollout. Just ask yourself: **Which manual Cornerstone tasks take up the most time for L&D and HR today, and what would we save if we could remove or simplify them?** ### What's been sitting on the wishlist? Not everything has to start with a problem. There are probably also things your team has wanted to do for years but never quite got around to. Maybe you wanted a better manager experience, more personalization, dedicated academies, better communications or a completely different way for employees to find learning. Perhaps an idea was discussed three years ago and dropped because it wasn't possible, was too complicated or simply wasn't a priority at the time. Get that list back out. A lot more is possible now than when many Cornerstone environments were originally set up. That doesn't mean everything on the wishlist suddenly needs to become part of the migration. Some things might make sense for go-live, others can follow a few months later and some may stay on the wishlist. The useful part is having the conversation now. You can decide what matters most, what would make the biggest difference and create a rollout plan that doesn't make the initial move unnecessarily complicated. How people find information is a good example of something that has changed. Employees are increasingly used to simply asking for what they need rather than figuring out which system, menu or search term will get them there. That's where something like [**Chatbot Studio for Cornerstone**](https://octily.com/products/chatbot-studio/) can become interesting. An employee can ask about training, see learning that is assigned or active, get recommendations, find the right Cornerstone page or search knowledge the organization has made available to the chatbot. That doesn't mean everyone needs a chatbot. It means something that might have sounded unrealistic a few years ago could now be a perfectly practical answer to something on your wishlist. Just ask yourself: **What have we previously wanted to do in Cornerstone but ruled out because it wasn't possible or practical at the time?** ### Are your reports answering the questions you actually have? Reporting is another area where it’s easy to simply recreate what already exists. But take a look at what happens after someone runs those reports. Are they actually being used as they are? Or are they exported to Excel, combined with another file, cleaned up and turned into something else before anyone can make a decision from them? And there may be bigger questions that your Cornerstone reports can't answer on their own. What is the relationship between learning and engagement? Where are skills gaps appearing? Are there patterns between learning, performance and other people data? Which areas actually need attention? That information often sits across different systems, which is why simply creating more reports in each individual platform doesn't necessarily solve the problem. With [**octo.taxi** (opens in a new tab)](https://octo.taxi/), Cornerstone data can be brought together with data from other HR and business platforms in one place. L&D and HR teams can then easily build their own dashboards around the questions they want to answer, explore the data and adjust what they want to see as their priorities change. You're not limited to a fixed set of dashboards or dependent on someone building a new report every time a new question comes up. Again, that doesn't have to happen on day one of your Single Architecture move. You might start by getting the foundations right and make better use of your data as a later step in the rollout. Just ask yourself: **If we had all the relevant data in one place, what would L&D and HR actually want to know?** ### So, fast migration or a little more time? There isn't one right answer. If your current Cornerstone setup works well, people can find what they need, managers have the information they need and your L&D team isn't fighting with manual processes, keeping the move lean could make perfect sense. But if you’ve answered some of the questions above and immediately thought of examples, it might be worth investing a little more time. And investing more time doesn't mean everything needs to be ready for go-live. You can use the migration to take stock, decide what you want your Cornerstone setup to become and then prioritize it. Keep the initial move focused, tackle the things that matter most and put the rest into a realistic rollout plan. That rollout doesn't have to begin with everyone either. Where possible, use Stage and Pilot to test the experience with different types of users before Production. Keep track of what has changed and listen to what employees and managers actually get stuck on. Maybe the first priority is the employee experience. Manager reporting could follow. A chatbot or new MicroApp might make sense once the new setup has settled in, while a wider data project could be something you work towards later. The point isn't to make the migration bigger. It's to make sure that once you're on the new architecture, you know where you want to go next. ### We can help with the move and what comes next At Octily, this can start with the **Single Architecture migration itself**. We help organizations migrate and optimize their Cornerstone setup, including reviewing what they have today, preparing for the move and looking at where the setup can be simplified or improved. That also means looking at what you already have. Existing customizations can be reviewed for migration risk, so you know what can carry forward, what needs attention and where rebuilding something creates an opportunity to improve it rather than simply recreate it. From there, we can also help turn some of those wishlist items into a realistic roadmap. That could include Cornerstone customizations, **OCE**, **MicroApps and Team Training Progress**, **Chatbot Studio**, or making more of your Cornerstone and HR data with **octo.taxi**. It doesn't all have to happen at once. The migration can be the starting point: get the foundations right, decide what matters most and roll out the rest at a pace that makes sense for your organization. [Read more about our Cornerstone Single Architecture migration and optimization services →](https://octily.com/consulting/) Or get in touch with us and bring your current setup, frustrations and wishlist. We’re happy to look at what makes sense for the migration and what could come next. [Read More](https://octily.com/consulting/) [Book a Meeting With Simen](https://octily.com/meet-simen/) ![Simen-Ling La](https://ebnnmeydktscnefergjm.supabase.co/storage/v1/object/public/client-logos/team/simen-ling-la.png) Simen-Ling La (Simen) Senior Project Manager 🇩🇪 Germany [(opens in a new tab)](https://www.linkedin.com/in/simen-ling-la-b11955152/) ![Simen-Ling La](https://ebnnmeydktscnefergjm.supabase.co/storage/v1/render/image/public/client-logos/team/simen-ling-la.png?width=168&quality=70&resize=contain) Written by Simen-Ling La October 21, 2026 Get notified about new articles Your browser asks for permission first. Delivery via OneSignal, details in our [Privacy Policy](https://octily.com/privacy-policy/#push-notifications). [Customization ### Change Management Support organizational transformation with customized change management pages and communication flows. Explore More](https://octily.com/customization/change-management/) ![Custom Pages](https://octily.com/assets/custom-pages-bg-1536w-BHDcseZs.webp) Customization ### Custom Pages Build any page you can imagine with fully custom layouts, content blocks, and interactive elements. Explore More [Customization ### Workforce AI (formerly Galaxy) Customize Cornerstone Workforce AI (formerly Galaxy) to match your HR strategy with AI-powered workflows and branded experiences. Explore More](https://octily.com/customization/cornerstone-galaxy/) ![Employee Engagement](https://octily.com/assets/employee-engagement-bg-CZN97gFI.webp) Customization ### Employee Engagement Boost engagement with dynamic, interactive pages that make employees want to return to the platform. Explore More ## Nice to meet you! Want to learn more about what we do? Let’s start a conversation. [Get in Touch](https://octily.com/get-in-touch/) [Book a Meeting](https://octily.com/meet)