Skip to main content

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice

PegaWorld | 28:00

PegaWorld 2026: From Notes to Blueprint to Infinity

Discover how Notes to Blueprint helps you rapidly understand your legacy estate and use Pega Blueprint to transform scattered business logic into future-proof, agentic workflows. Collaboratively design the future state of your most important processes and rapidly deploy them on a secure, scalable cloud architecture. Leave the data jails of the past behind and start your journey to a truly agentic enterprise.

It is 115. So we're going to get started and it's hard to see. But thank you everybody for showing up. I am very happy we got a good audience and also kind of a little bit surprised we're still here. Talking about Lotus Notes transformation in 2026. My name is Victor. I am senior director of Notes to Blueprint strategy, which means anything under Lotus Notes would fall under me. I also came into Pega about six months ago now, and through an acquisition of a company that I co-founded, where we've been doing domino migrations for a very long time. My name is Alex Exum. I am on the product marketing team for Platform. And so the last couple of years, I've been focused on how we can use AI, Blueprint, and some of our platform capabilities to help accelerate legacy transformation projects. So I started working with Victor earlier this year on some of the note stuff and it's yeah, it's exciting.

Um, before we jump into too much, I'm just going to give a quick overview of what we're covering. Um, so just a review. We're going to take a look at what's at stake, look at a couple metrics and take a look at kind of like the current state of things as it pertains to legacy transformation and transformation. Specifically. Um, Victor's going to give a walkthrough of how our approach to notes transformation is different. And what's unique about that. And we're going to get into some, some demos. So we'll see how you gain additional visibility and clarity into your notes estate with notes to Blueprint and that tooling, um, bring it into blueprint so that you can reimagine those legacy applications. And then the destination is the platform. So we're going to take a look at some of the new Infinity 26 capabilities and how they apply and how they can help accelerate these projects.

Um, before we get started or jump into that, I just want to level set a little bit. Um, because we know that AI and digital leaders are going to grow faster and, and, uh, modernized more quickly. Um, but a couple of years ago and even last year, this kind of manifested around fear of missing out or just enabling, um, adoption at any cost. Obviously now that conversation is shifting a little bit. Um, and, but the pressure is still mounting pressure to drive streamlined customer experiences across multiple channels to gain some of that agility from modernizing these projects. And, um, your legacy applications really can, can get in the way of that and can be a barrier. Um, because if you, if you don't understand what's in your legacy application, some of that business logic that's, that's built into it or even what some of the applications do, or if they're still in use, it can really inhibit your ability to, to modernize.

Um, and so, um, it can really be a barrier to, to innovation. Um, but we know that, you know, 40% of, of it spend is, is spent on technical debt. And so it's a real a real cost. But underneath the actual dollar value cost, it's really oftentimes about the opportunity cost. So that's money you can't be spending on modernizing. You can't spend it on becoming more agile for the future. You can't, you know, spend those dollars on adopting AI or becoming, you know, implementing automations to help streamline your processes because of these, because of the technical debt with legacy applications. So you're missing out a lot. And the cost of, of that grows every day. But underneath this sort of high level conversation around the opportunity cost and the blockers to agility, there's some nuance to some of the pain points that we're seeing with Lotus Notes specifically.

So, Victor, I know you obviously have a lot of experience there. So can you talk us through what that looks like? Yeah, I think what's interesting, I think you were spot on the point of like the cost of doing nothing is a big, you know, really the biggest cost. But the reality is, you know, to kind of level set a little bit, you know, Lotus Notes back in the days was a really good platform, right? It was good because you could pretty much turn it into whatever you wanted it to be, so you could build really advanced platforms and really advanced applications. The problem is when we now fast forward 15, 20 years, there's a lot of applications built that are poorly documented. You know, if they break, which you sometimes do, it takes a team of five to do the investigation to find which load script is not functioning properly, and it's really just holding it back.

So the other thing when, as Alex said, when we talk about AI is it's hard to implement and leverage that when your data is sitting in NSF databases. And that's really just the kind of top it up is like when I talk to customers, one of the key things I hear is how are we going to look after this? Like, it's fine today, but what about in five years? I think it's a while ago since they told people how to do lotusscript in college. I don't think they do that anymore. So it's getting harder and that risk is real, right? So some of the things that I've heard from customers recently is, you know, we made a decision ten years ago. We're going to move off of Lotus Notes. It starts with email and calendar and all that stuff. Sometimes you start with the easy applications, but then you look at a more I call them the hairy scary stuff and you're stuck.

Another example that I want to highlight, and we're going to get back to that one a little bit later, is I spoke to a pretty big bank out of Europe last week. Um, they have a couple of, a couple of applications still running on Lotus notes where they get, they have, they handle like automotive loans. Like anytime you apply for a loan for a car, it starts in a Lotus Notes application. The problem they have is when they look at this, they have to manually review each of these requests. And I asked them like, so how long does it take to to review each incoming request and then decide what to do? It takes about ten minutes to review the documents coming in before you decide what to do next, right? So when you do the math on that one 1000 cases every single day, ten minutes a case.

So we ended up coming to the conclusion that they spend about 160 man hours every single day reviewing incoming cases. So that's just one example of the type of processes that we often come across in, in Lotus Notes. And the reality is customers have tried. As I mentioned, most of them decided we're going to move off of Lotus Notes. We do the email, we then do the low hanging, low hanging applications. And then they got stuck. And the reason for that is you believe it's a lift and shift approach. So you try to we're just going to move these notes app into a new platform. And then you realize halfway through that it was way more complicated than you first thought. Right. Or even when you're successful in that and you post-migration realize that, oh, so what we did was we basically moved a pretty poorly, you know, built process from one platform to another.

And that's really not what we're trying to do here. So the way we're approaching this from a Pega perspective is very different. And it goes and, you know, you should have heard this in the keynote earlier today in a couple of different phases, right? The first phase with nodes to Blueprint. And we're going to get into the demo. So you get to see how this actually works is really to understand how this, you know, out of all these databases that we have, and I'm speaking to some customers that still have thousands and thousands of databases sitting in domino, which are the ones that actually matters, which are the ones that are business critical. So it starts on the discovery side to understand that and not only understand, you know, out of all these apps, these are the five or 10 or 25 that matters. But how are we actually using them all the way through the re-imagination, which we're going to come back to?

And then at the end, also data migration. How do we bring this valuable data with us? So to talk a little bit about a case that we'll be using today, which I mean, everybody here probably traveled in. So we all use some sort of travel approval system. We come across that use case quite often. So we're going to talk about a case like that. In this case it's a pretty manual process. You fill out a form, you then send it for approval. If the email gets delivered where you need to press the link to go in and approve or deny. So that's the use case that we're going to look at today, um, and see how we can not only transform it from Lotus notes, but actually also think about how do we make this better? How do we make it a better experience for the users and also for the business as a whole.

So with that, we'll get into the demo. Let's do it. So what you're going to be seeing here is notes to Blueprint. So notes to Blueprint is a technology that is being installed in the customer environment. So you install it on a workstation. We then use APIs to connect into domino. The first thing that we do. So it runs in a couple of different steps. So step one we call an inventory scan. So an inventory scan you basically point the product on the servers. So most customers have multiple servers. Some have a lot of them. Others have two for replication purposes. So we point on a server. We then collect all the databases running on that server. And the reason why that's important is already in that. And this takes, you know, an hour, sometimes an hour and a half. But it's a really fast process.

What that allows us to do is do the first filtering, right? So we can say these databases, nobody has opened in four years already at that point. You know, you don't have to spend more time on it. So it allows us to filter on which ones do we need to look at in more detail. So when we look at it in more details we actually collect who's using it. What are we using it for. Are we creating documents or are we just reading documents. We also look at the agents. A lot of the customers I talked to have many, many, many agents. But the reality is not all of them are being used, right? So an agent has to be super clear. It's not to be confused with like an AI agent, very different type of agent. So we look at how are we using it.

And that's very, very important. Before we talk about the re-imagination process, which is if you take everything that is sitting in a notes application and you push that into any new system, you're going to get a lot of stuff that you probably do not need. So it's about kind of seeing the trees for the forest. So at the end of the process, this technology is directly integrated with Blueprint. So it extracts the design of the application or the applications that you want to look at. And then it pushes that into Blueprint. Great. Yeah. I'm just going to summarize to make sure I'm following. So it's we have sort of a two phased approach on this getting to an application design and Blueprint. So first with notes to Blueprint. Sounds like we're analyzing the entire state, getting a lot more visibility into what those applications are doing, what they're used for, whether they're used at all.

We're taking everything that's still pertinent and relevant to the application design that we want to bring forward, and then we're leaving behind and archiving what we don't need. And then, you know, automatically integrating that into Blueprint. We're bringing that in so that we can then bring our, you know, our business folks, our IT folks together, import all of that rich analysis and design context that we need to not be starting from scratch. And, you know, you hit the ground running and also sort of bring these folks together to align on the outcome and the goal of the application. That's. Does that sound right? Yeah. No, absolutely. And I think the key thing to add to that, if you move to the next slide. Yeah, let's talk through that. There we go. Is the process, right? So the tool that we have at Pega now can do a lot of amazing things, including what we just talked about.

We still believe as part of collecting all this information. There's an element to that. And still, I would call it human in the loop. Like you need to make sense of the data that you collect. And the other thing too is we're not for, for most customers talking about one application, we're often talking about large scale and a large volume of apps. So as part of this process, it's really about, you know, looking at collecting information and write applications at the right time, using the human intelligence to define, okay, do I, what of this do I actually need? And then starting to report that so that you know what your scope is for transformation. So that's really the. And then at the end, once we know all of that, we can start Blueprint and start thinking about how do we make this experience and this application better.

Got it. That makes sense. So let's. Talk. About that. Yeah, I love it. Moving on to the Blueprint, as you can see here, as you jump over to from notes to Blueprint into Blueprint, you already have supporting assets over in the lower right that is bringing all that rich context from your notes application into, um, into your Blueprint. I'm going to hit play here. And so the functional description is filled out. I'm just filling out some of the details here and moving forward. Um, and so you'll see as we move through, I think I've sped this up a little bit. So just to, you know, cooking show style, um, but it generates your travel authorization workflow as well as others that might be relevant. You can, I'm sure if you've been in the Innovation Hub, if you haven't yet already, you're going to be making a lot of blueprints.

So get in there. Um, but I just did a quick overview to show that some of the business rules in your notes application are already coming through and you're able to see that workflow already. So, um, then jumping into the AI assistant, I'm kind of going through and working through, like, how can I assign an agent to automation in this process and just implementing it directly from the AI assistant. So able to build that right out and that first planning phase or approval, um, approval phase is just kind of a manual check now. And so you can kind of, um, automatically check for steps that have already been approved. And so that, that generates a recommendation for the approver to speed up that process. Um, and yeah, so kind of a simple, um, simple step change here, but as you said earlier, Victor, when you have thousands of cases that you're manually approving every day, um, those things can take up a lot of time over the course of even one day across an organization or over the course of a year.

Um, so jumping forward, just want to talk a little bit about why we can do this at scale and, um, within enterprise operations because we know that they're complex. Um, it's many different people, many different teams, disparate systems and handoffs. It can be really messy. So, you know, shoehorning in an AI solution or building something externally to then try to integrate can be difficult or not really get you the outcome that you need. Um, and we're able to do this because of, um, what we call our predictable agent orchestration. So if you were in the keynote earlier within the, you know, build and transform and run pillar, this is sort of a deeper view of the run pillar. Um, it really provides the structure and context and governance for agents to operate within because an agent that is in a silo, if it doesn't have access to the right data, or if it doesn't have the ability to, to execute or do certain things, it's not very useful.

On the other hand, if, if an agent has the wrong data access, too much data access, or the ability to do too many things, at best you might get a situation where the output is not very helpful at all. You know, everyone here has gotten slop responses from something that has access to too much data. Um, but then the cupcake, the cupcake dog, exactly. Which we love. He's cute, but not so useful. Um, and then, you know, on the, on the worst case scenario. It's a situation that might be a compliance or a regulatory issue. If you're operating outside of the guardrails that you want to set in place for your, for your organization. Um, but just to level set a little bit because now we go to importing the Blueprint into Infinity studio. And I know this is super fast, so don't mind me, this is a lab instance.

So I had to speed it up a lot. So it's faster in production. Um, but I've, I've set this up so it looks a little bit crazy. Um, but the import process is really the same as it was before. But your landing point is Infinity studio and the overall experience and the, um, the user experience, there will be something you're familiar with and you're able to navigate through similar to the Blueprint experience. So you see your workflows, um, all of your data integrations, both downstream and upstream personas, and it lands you on this auto generated implementation plan. But first, I just want to, I think I jump into the AI assistant and connect to your LLM provider of your choice. So that allows you to kind of utilize your own LLM provider and start to vibe code with, with your Pega application. So it brings a lot of the value and the speed and the agility of the vibe coding experience.

But it's not just a general code generation tool because it's contextually relevant to your Pega application, and it's built with our best practices in mind, you know, purpose built for enterprise standards. And you're able to, you know, the output is much more contextually relevant to the application that you're building or the workflow you're building. So I think here, I've just got a bit of an overview and start to, to build out some of the, some of the changes that you might want to implement and work with the AI assistant to kind of say, where should I start? What's the next step? Um, because you do, it does pull from that, uh, auto generated implementation plan, which is, which is great. Can I, can I just add one thing there, which is just to, to remind, like, what we're looking at here is still coming from that old notes application, right?

So as part of this process, we've gone from this old notes app that has been around for a while, leveraging all that insight fields, the forms, the logic, and we get all the way through Infinity where you can start basically chatting with your application. That is something that normally, and I've done a lot of these projects myself. It takes you 3 to 6 months just to get to that point. Just to just to add real quick. I think it's important to just tie it back to like, what are we actually looking at? This is all just programmatically coming from the notes application of choice here. Yeah. And being able to bring that in so quickly iterate with different teams in the design phase, and then immediately start building out and working through an implementation plan very quickly is really the, the main piece here. So, but yeah, just to level set a little bit around our thinking, which I know you saw some of this earlier today, but we really are thinking about agentic AI in these three key pillars.

So reimagining and transforming your applications with Pega Blueprint, which we saw. Um, and as especially critical for notes transformations and any transformation project. So the notes to Blueprint capabilities fit right in here. Um, and then in the build pillar we're implementing or incorporating Agentic AI. Um, that's really purpose built for enterprise grade application development. That's contextually relevant because we know that writing code and generating code is usually not the barrier to these transformation projects or, you know, transforming at scale. It's usually more so around, um, understanding your legacy systems more clearly, um, aligning stakeholders, designing for compliance and, you know, operating reliably at scale. So these are the hard things that, um, that come into play and, you know, the code generation less so. And so we've built it out around that model and it's all really in support of running predictable AI agents at scale across the organization so that they're reliable, in order to orchestrate humans, agents, systems all together in a way that's that's more predictable.

Um, so on that note, I think that. I just want to add one thing, which is to tie it back. So the example I made before around the incoming requests that have been manually reviewed, the conversation with our customers is really about how do we, you know, take away this whole manual process? How do we make incoming requests, an AI agent to review and extract information from the documents, making sure you have the right information in there? If not, you know, ask for more information. If yes, move ahead. Right. So it's it's simple examples like that when you're still on Lotus notes is really not possible, right? And that's really a conversation that I'm having is it's not about, to your point about how we can generate code based on notes, right? It's about how do we rethink the way we're building these applications. And most importantly, and it's something that You know, we see quite often where you have and maybe some in this room have as well.

We have multiple servers, multiple replicas of the same application, slightly different nuances to it across different regions. And then we think about, okay, so now we're going to transform. Do we want to migrate each and every one of those? Or do we really start thinking about how do we consolidate and how do we build one standard that you can then do nuances into instead, right? So it's about a different type of conversations. When I started with this 12 years ago, it was very much about how do we move from point A to point B? How do we bring that data across and just go rebuild it manually? Right? That's kind of what we've done. Now. We can take all of that, you know, things or code, whatever we want to call it. How do we take that intelligence coming from Lotus Notes that have been built up over 20 years, leverage AI to quickly understand it and start reimagining it on the fly.

The other thing that is amazing to me, I've seen this happening with customers is the, the, the nuance and experience where you can have a user actually try out their application really quickly. And I can say I've seen projects that have gone, you know, you start with some sort of analysis, mostly looking at how many lines of code do I have? And based on that, you say easy, medium or hard, right? And then you go, now we're going to build our first prototype. We'll come back in maybe three months, maybe six months before you can even start being hands on with it. With notes to Blueprint approach, you can go so fast from notes app to Hey Mr. Business user, try this out. Is this what you need? Right. And that makes a huge, huge difference. That's really what changes hearts and minds. Getting the live demo and being able to quickly see exactly what you're working with and what the how the application functions right from the design phase in Blueprint is huge.

Yeah. And most importantly, the other thing, which I'm going very off script, so I apologize for that. We're good on. Time. That I'm seeing a lot of is. And when you ask a customer, I'm sure maybe this will relate. Some of you like give us give us a medium to high complexity application. And like, yeah, this is a very complex one. I had a customer like three weeks ago. He said, yeah, we got this HR onboarding application really complex. I'm like, cool, we're going to take this one, push it through the process. We're going to show you what we can do with it. What we realized is there was no workflow whatsoever, right? Zero. It was literally the only function in the application itself was a button. Once you fill out your form, they send send forward to the next the approval for the onboarding process.

That was it. When we pushed that into Blueprint, Blueprint could actually realize that, hey, this should have been a workflow. These are the steps that you should have as part of the process. So it's not only about kind of looking at all those complex. Sometimes it's a simple applications that can make a big difference when we start thinking about what this should be. Because again, as we said in the very beginning, the way you build a notes app in 2002, and as then kind of built on top of and built on top of and, and changed slightly is very different from how you would build that sort of use case today. So I just want to kind of mention that as well, which I think is a key part of any, any legacy transformation. This is not just for Lotus Notes. This is really about kind of having a different mindset going into it, but most importantly, be able to go from end to end.

Yeah, I just wanted to add that on that topic. It's great because it really is about, you know, pulling the rich contextual information over layers and layers and decades of, of upgrades and builds into something that works for, you know, your modern enterprise. So yeah, no 100%. But if you do want to know more about this approach and what we're doing and or maybe talk about, you know, ask your questions in a slightly smaller forum. There is a booth in Innovation Hub where we are running live demos for different use cases where you can see end to end. The other exciting thing is the data migration capability. So we're not generally talking a lot about data migration, like actually being the system of record. But when we're talking about Lotus Notes projects, it's oftentimes the goal is decommissioning, right? But when we, you know, when I'm in conversations with large banks or insurance companies or, you know, public sector, local, state, whatever it might be, it's like, how do we do?

How do we go away from Lotus Notes if we still have data retention policies and we have stuff like that that we need to comply with. So we also have that data migration capability that once you've gone through the process of analyzing your state, extracting the design of your applications, reimagine the processes, moved it into Infinity. As a live production application. We can also bring open cases or old data with you into the new application as well, so that you can also see in Innovation Hub at the nodes transformation booth, get to see a live demo of that, which is really exciting. Um, and there's also a couple of sessions on this. There's a great session tomorrow with um, Navy, federal credit Union. Um, I know they replaced many, maybe hundreds. Don't quote me on that of, of notes applications and we're able to decommission.

Um, and so yeah, swing by tomorrow if you have have the chance. I know it's a great session. Yeah. And it's in my opinion, it's never the best thing is always to see somebody else that I've actually been able to do it right. And I think that's the key is like, I've heard this so many times in the last decade of like, yeah, we know we need to do this, but it's hard and it's costing us a lot of money because every app is going to take us two years, right? That's not the case anymore. Now we can do this fast one. I'll just make an example of a case that we did recently where it's like notes. Into production in 60 days for a relatively complex use case that's becoming reality. And it's not just because we're getting better at it. It's also because now we have AI that we can leverage in a good way, right?

So so that's what used to be almost an impossible task is now really, really possible. So this is one thing I want you to hopefully leave this session with. It's like customers are doing this. It's real. You can actually make it happen. Um, and we're seeing it and we're seeing it quite a lot of it, which is interesting. Yeah. And if you have, you know, specific use cases come by the booth, you're on your way there now. So let's, uh, awesome. And with that, I think we're going to give. Up a couple of more minutes to head to your next session. You wrap it. Appreciate everybody coming by. We're excited. Both Alex and I are here. So if you have questions or want to swing by the booth, feel free to do so. And thank you for joining. All right.

Related Resource

Product

App design, revolutionized

Optimize workflow design, fast, with the power of Pega Blueprint®. Set your vision and see your workflow generated on the spot.

Ready to build a Blueprint?
Choose the reinvention engine for your needs.
For workflows & app design

Reimagine your processes and turn any workflow into a build-ready application with confidence.

Pega Blueprint®
For marketing & CX strategy design

Visualize customer journeys and engagement strategies across all touchpoints and activate them.

Pega Customer Engagement Blueprint™
Share this page Share via X Share via LinkedIn Copying...