Good day, welcome to the MongoDB first quarter fiscal 2020 earnings call. Today's call is being recorded. At this time, I'd like to turn the conference over to Brian Denyeau, ICR Investor Relations. Please go ahead.
Thank you, Justin. Good afternoon, thank you for joining us today to review MongoDB's first quarter fiscal 2020 financial results, which we announced in our press release issued after the close of market today. Joining the call today are Dev Ittycheria, President and CEO of MongoDB, and Michael Gordon, MongoDB's COO and CFO. During this call, we may make statements related to our business that are forward-looking under federal securities laws. These statements are made pursuant to the safe harbor provisions of the Private Securities Litigation Reform Act of 1995, including statements related to our financial guidance for the second quarter and full year of fiscal 2020, our market opportunity, the impact of market trends on prospects for future growth, the benefits and impacts of recent acquisitions, the anticipated benefits of our products for our customers, and the opportunities presented by our partnerships.
The words anticipate, continue, estimate, expect, intend, will, and similar expressions are intended to identify forward-looking statements or similar indications of future expectations. These statements reflect our views only as of today and should not be construed as representing our views as of any subsequent date. We do not have plans to update these statements except as required by law. These statements are subject to a variety of risks and uncertainties that cause actual results to differ materially from expectations. For a discussion of the material risks and other important factors that could affect our actual results, please refer to those contained in our annual report on Form 10-K filed with the SEC on April 1st, 2019, our other periodic filings with the SEC. These documents are available in the investor relations section of our website at www.mongodb.com.
A replay of this call will also be available there for a limited time. Additionally, non-GAAP financial measures will be discussed on this conference call. Please refer to the tables in our earnings release on the investor relations portion of our website for a reconciliation of these measures to the most directly comparable GAAP financial measure. With that, I'd like to turn the call over to Dev.
Thanks, Brian. Thanks to all of you for joining us today to review our first quarter results. We are very pleased with our performance in the first quarter. Our great start in fiscal 2020 reflects strong execution by the MongoDB team and continued momentum across all aspects of our business. We're also benefiting from the previous product and go-to-market investments we made to ensure we fully capitalize on one of the largest market opportunities in software. In fact, IDC recently updated its forecast and expects the worldwide database software market to grow from $64 billion in 2019 to approximately $98 billion in 2023. We believe that much of this incremental $34 billion will come from modern applications and new workloads, which we are well-positioned to capitalize on.
Looking quickly at our first quarter financial results, we generated revenue of $89.4 million, a 78% year-over-year increase, and above the high-end of our guidance. We grew subscription revenue 82% year-over-year. Atlas revenue grew more than 340% year-over-year and now represents 35% of revenue. We had another strong quarter of customer growth, ending the quarter with over 14,200 customers. These results are a powerful indication of how MongoDB continues to benefit from a number of positive market trends. First, for a new platform to succeed, it has to be embraced by the developer community, given the disproportionate influence developers have regarding technology decisions. Our developer mindshare and financial results demonstrate that MongoDB has clearly established itself as the most popular modern database platform in the world.
Second is the growing recognition that because working with data is so critical when building applications, using a modern general-purpose database platform enables businesses across every industry to innovate faster and respond more quickly to new market opportunities. Customers are increasingly choosing MongoDB for their mission-critical workloads to drive innovation. Third is the increasing importance of being able to easily move applications across any compute environment. Customers want the flexibility to run applications on-premise, in a private cloud, and in the public clouds without being locked in with any cloud vendor. Moreover, we see a significant portion of our customers gravitating towards hybrid environments with a mix of workloads on-premise and in the cloud. With MongoDB, customers can run applications anywhere, in any compute environment, on the same data platform and feature set without having to rewrite any code.
We are at the early stages of the largest platform shift in history with the move to the cloud. Customers are still figuring out this transition. There are a number of approaches being taken. MongoDB provides complete optionality for customers to make this transition without locking themselves into a course of action and gives them the ability to make continuous adjustments. In short, customers can confidently future-proof themselves by choosing MongoDB. At MongoDB, we are always looking ahead at what's next and how the needs of our customers will evolve. To accelerate our mobile efforts, we recently acquired Realm, one of the most popular mobile database and synchronization platforms. Data synchronization is the single biggest challenge in building compelling mobile applications, and Realm has developed a comprehensive synchronization platform that is a natural complement to MongoDB Atlas and Stitch.
Realm reinforces our Run Anywhere strategy and, like MongoDB, is focused on giving developers a far more flexible, intuitive, and comprehensive way to work with data. We will be providing more details about our future plans for Realm and how it will create value for customers at MongoDB World later this month. Our growing popularity has made MongoDB an attractive partner for many companies. Expanding our partner ecosystem is a strategic priority and an area we have been investing additional resources. We had our strongest performance ever with partners in the first quarter, which reflects the healthy returns on investments we have made. Some highlights include our biggest quarter ever with systems integrators. We are seeing strong traction with these strategic partners in almost every region. Much of the deals SIs bring to us would most likely have involved longer sales cycles and smaller initial deals without their involvement.
Their trusted relationships give those customers the confidence to sign larger initial deals with us and to include MongoDB at the core of their digital transformation initiatives. We believe there's a significant opportunity to further deepen our relationships with SIs. We also signed several large deals through our IBM relationship, including a substantial win with one of the world's largest insurance companies. Last but not least, we were excited to recently announce an expanded partnership with Google, who will now be offering MongoDB Atlas as a first-class service on their Google Cloud platform. Being offered as a first-class service means Atlas will be integrated directly within the GCP console and marketplace, providing a unified user experience by tightly coupling Atlas with GCP's identity and access management, logging and monitoring, Kubernetes, and TensorFlow.
GCP customers will also be able to purchase and pay for Atlas the same way as any other GCP service and apply Atlas towards their spending commitments. We are moving forward with joint go-to-market efforts, and Google salespeople are highly incentivized to sell MongoDB Atlas, further extending our market reach. We believe this partnership is a clear indication that Google recognizes that to provide the best customer experience, it is important to integrate with the best-in-class products like MongoDB in the marketplace. I'd like to spend a few minutes reviewing some customer vignettes. The need to innovate and to provide a compelling user experience has become an imperative for companies in every industry around the world. We believe companies that are not leveraging a modern data platform like MongoDB for mission-critical applications are increasingly at risk of being at a competitive disadvantage.
The following are a small sample of the customer wins and interesting use cases from the first quarter. When Splunk needed robust handling for non-relational data to complement their extensive IP, they naturally chose MongoDB. Splunk embeds MongoDB into the search head component of every deployment of MongoDB Splunk Enterprise to store application state and configuration data. TIM, formerly Telecom Italia, a leading telecommunications provider in Italy, is adopting MongoDB for their customer usage data, which was traditionally stored on a relational database. MongoDB is also used within their new service delivery platform as one of the fast data layers to guarantee quick access to information. Renewable energy provider, Enphase Energy, is a global energy technology company and the world's leading provider of solar microinverters. They decided to migrate from DynamoDB to MongoDB Atlas.
Atlas will provide Enphase with the ability to reduce risk, automate processes, scale elasticity, and meet their future global availability needs. Auto Trader U.K., the U.K. and Ireland's largest digital automotive marketplace, has been using MongoDB since 2011. They recently made an internal decision to move to the cloud and saw immense value in using MongoDB Atlas for removing the operational overhead of their existing deployment. Everbridge, a leader in critical event management and enterprise safety software applications, utilizes MongoDB as the core data platform within their suite of products. MongoDB underpins their high availability strategy, which enables them to move data globally without sacrificing scalability or performance. As Everbridge continues to expand geographically and deal with ever-growing regulatory requirements, MongoDB is a key component enabling flexibility with their application architecture.
FanFight, a fantasy cricket league based in India, built their business on MongoDB to accommodate the dramatic fluctuation in concurrent users, anywhere from 10,000 to 100,000, depending on the team or the match. They chose MongoDB Atlas to get a better insight into real-time monitoring, improve their scalability, lower response times, and take their platform to the next level. To be clear, customers are increasingly turning to MongoDB to increase their pace of innovation and improve business performance. Innovation is the core of what we do at MongoDB. From the very beginning, we have focused on creating a better way for customers to work with data to improve their business performance. We were pleased to have been named a leader in the 2019 Forrester Wave for Big Data NoSQL, where they gave us top marks for our ease of use, simplified model, on-demand elastic scale, multi-cloud support, and comprehensive tooling.
We were also named a leader in the most recent Forrester Wave for Database-as-a-Service, where we received top marks for high availability, disaster recovery, multi-model support, automation, user access, roadmap, and 6 other categories. I will note that the only other vendors to be named a leader in this category were AWS, Google, Microsoft, and Oracle. We look forward to sharing our vision and many specific product announcements at MongoDB World, our annual user conference taking place in New York on June 18th, and hope to see many of you there. Before I turn the call over to Michael, I wanted to provide an update on some changes being made to our board of directors. Kevin Ryan, our current board chairman and one of our co-founders, will not be continuing as a director after our annual meeting of stockholders on July 10th, 2019.
From working with our other co-founders, Eliot Horowitz and Dwight Merriman, to create the document database model, to helping raise capital in the company's early years, to his wise strategic counsel as our board chairman, Kevin has had a big impact on MongoDB over the last 11 years. Kevin will be devoting his time to the number of other early-stage companies he's incubated and developed over the past few years. On behalf of everybody at MongoDB, I want to thank Kevin for everything he's done for the company and wish him all the best in the future. I'm excited to announce that our board has named Tom Killalea as its next chairman to take over when Kevin's term as director expires.
A member of our board since 2015, Tom is one of the world's foremost cloud computing experts and one of the original executives in charge of creating and scaling AWS. Tom is a visionary with a deep understanding of how companies are looking to leverage technology, and in particular the cloud, to transform their business. Tom has been a terrific asset to our board, and I would like to congratulate him on this new role. We anticipate that the board will be appointing Archana Agrawal as a director later this summer. She's currently the head of enterprise and cloud marketing at Atlassian, where she leads global marketing for all products. Prior to this role, Archana served as Atlassian's head of data science and growth marketing, where she helped build and scale the analytics capabilities for the high-velocity self-serve go-to-market model. We are excited to welcome Archana to the board.
To summarize, MongoDB got off to a great start in FY 2020. Our market position continues to strengthen, and customers are increasingly turning to MongoDB as one of their strategic vendors. We are confident we have a long runway to drive high levels of growth for years to come. With that, let me now turn the call over to Michael.
Thanks, Dev. As mentioned, we're very pleased with our first quarter performance, which reflects best-in-class growth at meaningful scale. I'll begin with a detailed review of our first quarter results and then finish with our outlook for the second quarter and full FY 2020. As a reminder, starting this quarter, we are only reporting our current and historical financial results on an ASC 606 basis. For convenience, we have also included in our earnings release an additional table with our historical customer count data. I'll now turn to our first quarter results. Total revenue in the quarter was $89.4 million, up 78% year-over-year. Subscription revenue was $84 million, up 82% year-over-year. Professional services revenue was $5.4 million, up 33% year-over-year.
As a reminder, our first quarter results include the impact of mLab, which we acquired in November 2018 and performed in line with our expectations. Excluding mLab, the organic growth in the business remained very strong, consistent with the last few quarters, and we are very pleased with our first quarter results. The strength in the quarter was broad-based across geographies, industries, and use cases. We are pleased with the increasingly strategic nature of our customer wins, which is driving larger new logo additions and continued strength in upsell activity. We're also seeing rapid adoption of Atlas, which grew over 340% in the quarter and now represents 35% of total revenue, compared to 14% in the first quarter of FY 2019 and 32% last quarter.
During the first quarter, we grew our customer base by over 800 customers, bringing our total customer count to over 14,200, which is up from over 6,600 in the year-ago period. Of our total customer count, over 1,800 are direct sales customers, which compares to over 1,550 in the year-ago period. The growth in our total customer count is being driven in large part by Atlas, which had over 12,300 customers at the end of the quarter, compared to over 11,400 at the end of the fourth quarter. The sequential growth in total customers includes growth in our Enterprise Advanced customers, as well as new Atlas customers. It is important to keep in mind that the growth in our Atlas customer count reflects new customers to MongoDB, in addition to existing Enterprise Advanced customers adding incremental Atlas workloads.
We also continue to see healthy expansions from existing customers, which is a key component of our growth strategy. Our net ARR expansion rate in the first quarter remained above 120% for the 17th consecutive quarter. We ended the quarter with 598 customers with at least $100,000 in ARR and annualized MRR, which is up from 394 in the year-ago period. Moving down the P&L, I will be discussing our results on a non-GAAP basis unless otherwise noted. Gross profit in the first quarter was $62.8 million, representing a gross margin of 70%, compared to 74% in the year-ago period. As expected, the biggest impact on gross margin in the quarter was the increased revenue share from Atlas, in addition to the acquisition of mLab, which has a lower gross margin than Atlas revenue.
We expect the impact from mLab to dissipate by the end of fiscal 2020 as we migrate mLab customers to Atlas. We continue to see gross margin improvement of organic Atlas as this business scales. However, we continue to expect that we will see some modest reduction in overall company gross margins as Atlas continues to be a bigger portion of our revenue. Our operating loss was $12.6 million, or a negative 14% operating margin for the first quarter, compared to a negative 38% margin in the year-ago period. The more than 2,300 basis points in improvement in operating margin is particularly impressive given our growth profile and the investments we are making in the business. Net loss in the first quarter was $12.1 million, or $0.22 per share, based on 54.7 million weighted average shares outstanding.
This compares to a loss of $0.37 per share on 50.4 million shares outstanding in the year-ago period. Turning to the balance sheet and cash flow. We ended the quarter with $476.9 million in cash equivalents, short-term investments, and restricted cash. Subsequent to the end of the quarter, we acquired Realm for $39 million. Operating cash flow in the first quarter was positive $3.2 million, driven in part by the collections from strong fourth-quarter bookings. After taking into consideration approximately $400,000 in capital expenditures, free cash flow was positive $2.8 million in the quarter. We are pleased to have generated positive free cash flow for the first time as a public company. Of note, this occurred earlier than we had expected and reflects the scalability of our business model.
As a reminder, we would expect the second quarter to be our largest cash burn quarter due to seasonally lower first quarter bookings and incremental expenses related to our MongoDB World event. Despite the strong Q1, we continue to expect that we will burn cash in full fiscal year 2020 as we continue to invest significantly in the business. Short-term deferred revenue was $128.3 million, up 47% year-over-year, while total deferred revenue of $143.7 million is up 39% year-over-year. Please note that the adoption of 606 materially impacts our deferred revenue balance, and quarter-to-quarter comparisons of deferred revenue can also have some level of variability due to timing. As Atlas is a usage-based model, it generates less deferred revenue than Enterprise Advanced.
As a reminder, the majority of Atlas revenue is billed monthly in arrears versus the annual in-advance billing terms we see with our Enterprise Advanced customers. For example, currently, approximately two-thirds of Atlas revenue is not reflected in deferred revenue. Given these invoicing dynamics and Atlas' increasing share of our overall business, we believe looking at growth in deferred revenue is becoming even less relevant in evaluating our business. I'd now like to turn to our outlook for the second quarter and full fiscal year 2020. For the second quarter, we expect revenue to be in the range of $90 million-$92 million. We expect non-GAAP loss from operations to be negative $16.5 million to negative $15.5 million, and non-GAAP net loss per share to be in the range of negative $0.29 to negative $0.27, based on 55.4 million weighted average shares outstanding.
For the full fiscal year 2020, we now expect revenue to be in the range of $375 million-$381 million, compared to our previous guidance of $363 million-$371 million. As a reminder, year-over-year growth comparisons and quarter-to-quarter results will likely be more variable under 606, due in part due to the timing of multi-year contract signings. As an example, and as we have described before, we are facing noticeably larger compares in the second half of fiscal 2020, particularly in the third quarter. In addition, the fourth quarter will be the first quarter where we'll have mLab in the base period, and as we have described before, we have expected some deterioration in the revenue from former mLab customers.
For the full fiscal year 2020, we expect non-GAAP loss from operations to be negative $63 million to negative $59 million, and non-GAAP net loss per share to be in the range of negative $1.11 to negative $1.04 per share, based on 55.6 million weighted average shares outstanding. Please note that our updated earnings guidance reflects the impact of the Realm acquisition, which we completed in early May. Realm will have a de minimis impact on revenue. There are two factors to call out in our operating loss outlook. Better-than-expected performance in the core business, more than offset by the additional expense associated with Realm. To summarize, MongoDB continues to perform at a very high level. We are delivering growth at scale that few companies can match. We are disrupting one of the largest markets in software, and we're well-positioned to drive high levels of growth for the foreseeable future.
With that, we'd like to open it up to questions. Operator?
Well, thank you. If you would like to signal with questions, please press star one on your touchtone telephone. If you're joining us today using a speakerphone, please make sure your mute function is turned off to allow your signal to reach our equipment. In addition, please limit yourself to one question and one follow-up question. Again, that's star one for questions. Our first question comes from Raimo Lenschow with Barclays Capital.
Hey, thanks for taking my question, and congrats for a great quarter.
Thanks, Raimo.
Dev, I apologize for the question already, but can you talk a little bit about Realm? When we talk with the guys in the field, they were super excited about it because they say, "Look, mobile is a really important part of what's going on," but I'm not quite sure I fully get it. Could you just talk me through that? I have a follow-up for Michael.
Yeah, sure. Much like the founders of MongoDB, Realm's founders came from Nokia, so they had a lot of experience building databases for mobile devices, especially feature phones, and they saw all the challenges with those legacy solutions. They built a database optimized for the mobile device, including a very sophisticated data synchronization protocol to basically synchronize data back and forth from the mobile device to the back-end server and vice versa, especially dealing with slow or intermittent connections. Moreover, they built a very sophisticated API, so as data changes, the UI would be updated in real time. The trend now is to build these very rich mobile applications that represent data in real time, and data is the biggest challenge with mobile. We were very attracted to Realm because of the developer mind share they have.
Much like MongoDB, their data model is very similar to ours, and so they had a lot of developer traction. We will be making some specific product announcements at MongoDB World about how we're integrating Realm into the larger MongoDB platform.
Okay, perfect. That helps. Follow-up from Michael. Michael, as you said, two-thirds of Atlas revenue is not in deferred. Is there a way to think about maybe ARR or something to kind of give us more visibility? What's the best way you suggest for us to track the progress?
Yeah. I think as we've talked about before, it continues to be revenue is the core way of looking at it. We're trying to provide sort of additional slices given both the self-serve nature as well as the sales-sold nature. As we've talked about before, specifically looking at deferred really winds up missing the picture, which is why we wanted to provide the incremental sense for the order of magnitude of how much of Atlas currently is not flowing through deferreds.
Okay. Perfect. Thank you. Congrats.
Thanks, Raimo.
Thank you.
Next will be Sanjit Singh with Morgan Stanley.
Thank you for taking the questions, congrats on another excellent quarter.
Hey, Sanjit.
Dev. Hi, Dev. How are you?
I'm well.
Maybe just to start off on, a follow-up to Raimo's question on serverless. Can you give us a sense of where serverless adoption in terms of workloads are versus maybe containers and the Kubernetes movement? Is this lagging by a year or two? What's the uptake on serverless, and probably outside of AWS, is that beginning to start to gain some traction as well?
Yeah. Obviously, serverless got a lot of hype a couple of years ago. I would say we're just starting to see customers really start adopting serverless. It's still very early days. Frankly, our announcement of Stitch was our version of serverless, which is a much more sophisticated version than, say, Lambda, with the capabilities we had in terms of providing data access, and being able to integrate to other third-party services. I would say that it is a trend that we foresee in the future, an increasing trend in terms of how applications are built, and that's something that we're planning for.
Excellent. Then maybe just to sort of mark-to-market on some of the trends around MongoDB overall and Atlas. I remember at the time of IPO, we were talking about most of the use cases around the document models supporting transactional applications. There was a potential opportunity to get more analytical workloads and maybe graph database workloads. Where are we in terms of that multimodal adoption as customers sort of subsuming multiple use cases onto the database platform? Any sort of color there.
Yeah. We believe that the document model is a superset of the relational and the key-value store. For example, we support joins. We have far more functions than a key-value store, though we can mimic a key-value store, especially with the tunability of our consistency model. Then in terms of analytics, in fact, we recently announced on Atlas analytics nodes, where you basically have now read-only secondaries, where you can use our BI connector to run reports on your production workloads without impacting user performance. This is something that other databases just cannot do. That is something that we support, and you're going to see Atlas continue to be a big part of the MongoDB story going forward.
Excellent. Looking for the analyst day.
Cool.
And our-
Looking forward to seeing you then.
Thank you. Our next question come from Heather Bellini with Goldman Sachs.
Yeah. Hi, Dev. I was wondering, there's been a lot of, I guess, challenges in the overall infrastructure software market, obviously predominantly the on-premise vendors over the last couple of prints that we've seen over the last few weeks. I was wondering if you could share with us kind of anything you're noticing from a deal-closing environment, or just kind of commentary on overall IT spending that you could share with us that you're hearing from customers. Also, if there's anything that you could share with us just about how you've seen customers respond. It doesn't seem like AWS's offering is gaining much traction, just if you've heard from any customers about feedback and if it comes up in any customer conversations at all. Thank you.
Yeah. On the infrastructure spending environment, we feel very good about the environment. In fact, we just finished up our QBRs with our sales teams around the world, a big push is to recruit more aggressively because we see a very big market opportunity in front of us. We feel very good about our positioning. We feel very good about our competitive advantage against all the alternatives or substitutes out there. We're seeing more and more customers adopt us for mission-critical workloads, it's not just a North American phenomenon. We're seeing that in EMEA, LATAM, and Asia Pacific region. We feel really good about the trends that we see.
Part of that reason is that if you think about what's happening in the macro environment, the way apps are being built and the decomposition of monolithic apps into microservices, the move to the cloud and the need for a hybrid environment, the desire to consume infrastructure as a service, the desire to support a multi-cloud environment all play to our strengths. I think the recognition that the document model is the easiest way to work with data. We feel really good about that, while this is a big market, obviously, it attracts a lot of big competitors. We don't see any changes in the competitor environment. I must remind you that this is not a winner-take-all market, other vendors don't have to die for us to win, we feel very good about the market trends and the opportunity in front of us.
I just had a follow-up, if you don't mind. Atlas now is, I think you said it was 35% of total revenue. If you look out three years, what do you expect that to be? How do you see that growth trajectory on a % of revenue basis kind of continuing?
It's hard to answer that question with any level of specificity, but I'll tell you directionally that we definitely believe the future is in offering cloud services. As we've mentioned in the past, a few quarters ago, Atlas and Enterprise Advanced were at feature parity. Now we're leading with new features on Atlas itself, so you'll actually see new features introduced on the Atlas platform before it gets incorporated back into our on-premise product. We're big believers in the move to the cloud. We're big believers in the fact that customers will not want to put all their workloads in one basket, so a multi-cloud model will be important. For larger customers who made large investments in their own infrastructure that are sunk costs, they'll want to also have a hybrid environment of an on-prem cloud environment. We think we're well-positioned there as well.
Great. Thank you.
Thanks, Heather.
Next will be Brad Reback with Stifel.
Great. Thanks very much. Dev, maybe sticking with Atlas first, can you give us a sense of what the net expansion rate looks like in that business versus the overall business, maybe on a cohort perspective?
Yeah. The net expansion rate is definitely higher than our overall blended business. We don't publish that number, but it's just a function of the fact that customers can consume infrastructure more quickly. They don't have to go provision more internal capacity or deal with any of the operational issues of provisioning more capacity. We find that the net expansion rates are higher than our blended rate that we've disclosed, which is for the 17 quarters in a row, has been over 120%.
Great. Just following up on your commentary around the SIs and the strong traction you're seeing there, are there any commonalities around use cases, verticals, geographies? Thanks.
Yeah. I would say the commonality is that customers are increasingly using SIs as their application development arm, and they're obviously at the forefront in terms of how applications are being built. There's a natural synergy between us and them, because as they build apps and they choose MongoDB, that drives revenue for us and obviously drives meaningful application development revenue for them. There's a natural synergy between us and the larger SIs, and we're working with a number of them. People like Accenture, Capgemini, Infosys, TCS, Cognizant, and a bunch of boutique vendors all around the world. The use cases are quite varied. There's some SIs that are focused on the financial services sector or the healthcare sector. Others are more horizontal, others have more of a geographic focus. It really depends on the partner.
We typically try and work with a partner that's best positioned in a particular customer account. We have, obviously, some strategic relationships that span all theaters, and it just depends on the situation of who we partner with.
Excellent. Thanks very much.
Thanks, Brad.
Next will be Brent Bracelin with KeyBanc Capital Markets.
Hi, this is Clark Jeffries on the call for Brent. Maybe Dev, for you, as you start to invest in these technologies, maybe outside of the core document database, what are the core considerations that you're mulling over as you choose technology? What do you see as will have an everlasting benefit to the developer? Do you see there being plenty of opportunity to be tactical on just relieving the pain points with the legacy technology?
Yeah, our vision is that we want MongoDB to be the best platform to build modern data applications. That's our overriding strategy. I will tell you that I don't want to steal our thunder from MongoDB World. We'll be making some very interesting announcements there. As I mentioned, we'll be talking about how we plan to integrate Realm into the core platform and a bunch of other new announcements. It's all in the spirit of making MongoDB truly the best platform to build modern applications.
Great. Michael, just given the relative strength of maybe the Enterprise Advanced business and deferred revenue, were there any significant multi-year deals signed in the quarter that may have been a benefit to revenue? As you look at the full year, is that 5% contribution to this year changing at all? Thank you.
Sure. Yeah, no, I think as we said in the prepared remarks, as we've seen pretty consistently over the last several quarters, the performance is quite broad-based. Whether that be by geography or product line or channel, however you want to think about it's really been quite broad-based and Enterprise Advanced had yet another good, strong quarter, as well. There was not a disproportionate amount of multi-year deals relative to what we would've expected, in this quarter. I don't know what the 5% that you're talking about is. I don't know what that reference is.
I think last quarter commentary on maybe multi-year contribution to revenue being about 5% for the full year.
Yeah. The 5%, just to be clear, it wasn't multi-year, it was just simply the impact of ASC 606 relative to ASC 605. It wasn't a multi-year comment in general, but it was just the impact of including the term license component as opposed to everything be ratable.
Yeah. Understood.
Yeah. No, we haven't seen anything that would have us alter that view.
As a reminder, if you would like to signal with questions, please press star one. Again, that's star one for questions. The next question will come from Ittai Kidron with Oppenheimer.
Hi, this is Vinod Srinivasaraghavan on for Ittai. Thanks for taking my question and congrats on the quarter. I just want to talk about the SSPL for a second. How are your talks with industry stakeholders going, and can you comment on any future licensing changes at this time? Thank you.
Yes. Just to make sure everyone is up to speed, all our products today are licensed under SSPL. We did withdraw ratification of the SSPL with the OSI because we thought it'd be best to just work with them on coming up with a license that would basically meet our needs, but as well as let the OSI help drive the formulation of a new license. If it's consistent in principle to what SSPL, we will end up potentially adopting that new license. I should note that we've already seen a number of other vendors come out with their own licenses that are somewhat consistent with the spirit of SSPL. I expect this trend to continue. In terms of our discussions with other people, for our customers, it's been a complete non-event.
Our partners have been very supportive, and we feel very good about the defensibility of our IP.
Great. Thank you.
The next question comes from Rishi Jaluria.
Hi, guys. This is Hannah on for Rishi. Thank you for taking my questions. Just starting off, I know last quarter you were talking about adding sales capacity in the field and growing the self-serve business, I was just wondering if you could give an update on that and any new initiatives you've announced on that.
Yeah. We are definitely trying to add a lot of sales capacity. We're actively recruiting in all theaters around the world. We've added leadership capacity, which is a precursor to adding field capacity. We're spending a lot of time not just on recruiting, but also on the onboarding program so our new reps the ramp to productivity is as short as possible. We're spending a lot of time on training and other development activities, not just for reps, but also for our leadership. In terms of self-serve, that's also a big push. There's a lot of focus on our self-serve business. We've added a number of resources to that team. It's a big part of the senior management's attention and focus. You'll expect us to add more capacity in that group.
As I mentioned in my prepared remarks, Archana Agrawal, who's going to be joining our board in August, she ran and built the self-serve capabilities at Atlassian. The reason her experience is very relevant, because that was a developer-focused product. Their business is predominantly self-serve. Her experience, and she's obviously worked in a very high-growth, rapid growth environment. That experience will be very relevant to what we're doing here, and we're excited to get her assistance and counsel as we scale our business.
Okay, great. That's really helpful. Second, I was wondering if you had any commentary around churn you're seeing from the mLab customers.
Yeah. What we've talked about is it's less about churn as we gave our forecast and our guidance. It's more about price compression as resulting of the fact that we offer different pricing plans, and our philosophy has been to be customer friendly, and if they had a lower plan previously, they would get the benefit of the lower plan. If the Atlas plan represents a price reduction, they would get the benefit of the Atlas price reduction. So far, the integration has gone smoothly. We're only a couple quarters into it, and most of the migrations will take place in the latter half of this year.
I don't think there's anything material to report there, but so far, we've been very pleased with how things have gone and the performance of mLab and the integration steps that we've made over these first two quarters.
Okay. Thank you.
Thank you. That does conclude today's question and answer session. I'll now turn the conference back over to Dev Ittycheria for any additional or closing remarks.
In summary, we're really pleased with the start to fiscal 2020 with our Q1 performance. We believe the investments we're making in both the product and go-to-market areas are yielding high returns. We're really excited about the future. We thank you for your time, and we hope to see many of you at MongoDB World in New York City on June 18th, 2019. Thank you.
Thank you.
Well, thank you. That does conclude today's conference. We do thank you for your participation. Have a wonderful day.