Cycle on May 24, 2026

I will begin by listing the open threads of interest for this topic to understand what specific areas or questions need to be pursued in this research cycle.

I will search for information on how AI-native ERPs like Rillet, Campfire, and DualEntry address historical data migration and the automation of mapping financial data from legacy systems like SAP and NetSuite.

Let's fetch the Rillet case study for OnlineMedEd migrating from NetSuite to Rillet, and the Rand Group NetSuite vs Rillet comparison. I also want to search for Campfire and DualEntry. First, let's fetch the OnlineMedEd case study to understand the migration process and implementation. I will also fetch the Rand Group page.

Let's fetch the Rand Group NetSuite vs Rillet comparison. Then I'll search for Campfire and DualEntry. Let's do a search on how these platforms handle data migration, AI ledger mapping, or automatic data ingestion. Let's start with the Rand Group article.

Now I'll perform a web search on Campfire ERP, DualEntry, and Rillet in the context of data migration, ingestion, or mapping. Let's do some searches. Let's find out how Campfire ERP and DualEntry handle migrations. I will also search for how Rillet automates historical data migration. Let's run a search.

Let's fetch the LinkedIn pulse article "Campfire ERP: The AI-First Revolution in Enterprise Finance" and Rand Group's "NetSuite vs. Campfire: Which ERP is built to scale?". I would also like to see the Reddit thread "Anyone have a take on the next gen ERPs?" to get actual user/practitioner perspectives. I will fetch those three. Let's start with the LinkedIn pulse article and the Reddit post. Or let's do a search specifically for "DualEntry" data migration or legacy platforms. Let's fetch the LinkedIn article first.

Excellent. Now let's search for the Reddit post "Anyone have a take on the next gen ERPs? : r/FPandA - Reddit". I'll use the search tool to find the URL, and then fetch it. Let's do a search on Reddit for "next gen ERPs" or "Rillet, Campfire, DualEntry".

Excellent, let's fetch the Reddit thread `https://www.reddit.com/r/FPandA/comments/1oenyal/anyone_have_a_take_on_the_next_gen_erps/` to read what FP&A professionals are saying about these next-gen ERPs and if they mention details about data migration, mapping, or implementation bottlenecks.

Ah, Reddit is blocked or not supported by the fetch tool. That's fine. We can search for other sources or use search queries that might extract snippets, or we can look for other industry articles or blog posts discussing these tools. Let's do a search on how these next-gen ERPs (Rillet, Campfire, DualEntry, Everest) handle data migrations, ledger mapping, and automation. Let's run a query to find out more about DualEntry, Campfire, or Rillet's technical details regarding data migration, ingestion, and mapping. This is directly related to the open thread: "how are these startups using AI to automate the transfer and mapping of complex historical financial data?" and "what are the primary data migration and implementation bottlenecks for enterprises?" Let's search for: `Rillet "migration" OR "mapping" OR "ingestion" AI` `Campfire ERP "data migration" OR "mapping"` `DualEntry "data migration" OR "mapping"` Let's do some searches.

Wow, this is incredibly valuable! Let's look at the results: 1. `RoboCFO.ai` has an article "7 AI-Native ERPs Rated for CFOs (2026)". It says: "DualEntry, Campfire, Rillet, Everest Systems ... 'NextDay Migration' promises full historical data migration in 24 hours using an AI-powered mapping engine." Wait, let's fetch the RoboCFO.ai page: `https://robocfo.ai/frameworks/ai-native-erp-landscape` Or let's find the URL for the Contrary Research breakdown of DualEntry: `https://research.contrary.com/company/dualentry` Let's also look at `https://www.versori.com/post/5-ai-native-erps-reimagining-enterprise-software` which mentions "Its NextDay Migration tool can map and port historical data from legacy systems within 24 hours... DualEntry..." Let's fetch these pages. They contain exactly what we need to answer the open thread about how startups are using AI to automate the transfer and mapping of complex historical financial data, and what the primary bottlenecks are. Let's fetch RoboCFO.ai first.

Ah, the fetch failed on RoboCFO.ai. Let's try to fetch the Contrary Research company profile for DualEntry: `https://research.contrary.com/company/dualentry` Let's also do a web search for: `"NextDay Migration" DualEntry` `DualEntry "Contrary Research"` Let's see if we can fetch the Contrary Research page.

It seems Firecrawl/scrape is running into timeouts or experiencing issues. Let's do a google search with `web_search` and ask for more specific queries, or try to fetch smaller pages, or we can use search terms to get rich snippets. Let's search for: `"DualEntry" "NextDay Migration"` `"DualEntry" "migration engine"` `"DualEntry" "Contrary Research" "migration"` Let's search for those.

This is fantastic! Let's fetch the DualEntry funding announcement page, which will have details about their "NextDay Migration" engine and how it works: `https://www.dualentry.com/funding-announcement` Let's also fetch the Contrary blog post "Investing in DualEntry": `https://contrary.com/blog/investing-in-dualentry` Let's hope these fetches work. If they don't, we can try other sources or search queries. Let's start with `https://www.dualentry.com/funding-announcement`. Or we can search for the text of that announcement to get quotes. Let's try fetching first.

This is phenomenal evidence! Let's analyze what we have here. We have: 1. DualEntry raising a $90 million Series A in October 2025 from Lightspeed Venture Partners, Khosla Ventures, GV, Contrary, and Vesey Ventures (bringing total funding to over $100M). 2. Their solution "NextDay Migration™" is powered by the "world's first ERP migration engine." It gets teams live with its full accounting suite in 24 hours, migrating every line item, subledger, and attachment seamlessly and securely from NetSuite, Sage Intacct, SAP, Microsoft Dynamics, Great Plains, QuickBooks Desktop, Peoplesoft, QuickBooks, and Xero. 3. This directly addresses the open thread: "how are these startups using AI to automate the transfer and mapping of complex historical financial data" and "what are the primary data migration and implementation bottlenecks for enterprises". Wait, let's search for how this "NextDay Migration" engine actually works technically. How does it map the data? Let's search for: `"NextDay Migration" OR "ERP migration engine" AI mapping "DualEntry"` Or let's search for: `DualEntry "NextDay Migration" how it works OR technology` Let's run a search.

Let's find the Reuters article about DualEntry raising $90 million, which might give us more details: `https://www.reuters.com/technology/company-valued-415-million-2025-10-02/` (Wait, the URL in the search result is: `https://www.reuters.com/technology/company-valued-415-million-2025-10-02/` — let's check it). Let's also search for how Campfire handles data migrations. In the LinkedIn article about Campfire, it mentioned: "Campfire has demonstrated expertise in migrations from legacy systems, particularly Sage Intacct, with faster migration timelines compared to traditional 6+ month ERP implementations." "Our typical customer migrates to Campfire from QuickBooks and Xero, but we've also migrated customers from mid-market ERPs like Sage Intacct and NetSuite." "Brian Ehrlich, Finance Director at Flex, implemented Campfire entirely in-house twice, closing books within three weeks of signing both times. This represents a significant improvement over traditional ERP implementations that often require 6+ month and extensive consultant involvement." Wait, let's search for: `Campfire ERP "data migration" OR "implementation" OR "migration engine"` Let's run a search.

Let's search for: `"has anyone implemented campfire ERP before? : r/Accounting"` Wait, the Reddit post on r/Accounting says: "We looked at Campfire and are most likely going with Rillet or Dual Entry. I was somewhat surprised how all three of them made implementation..." Let's see if we can get a search snippet or details from that Reddit post to see if there are any specific quotes or comments. Let's do a web search with: `site:reddit.com/r/Accounting "implemented campfire ERP"` Let's see if we can retrieve more details.

These Reddit thread titles are very illustrative: 1. `has anyone implemented campfire ERP before? We are currently onboarding to campfire and it has been an absolute disaster. We liked the...` 2. `thoughts on ai-native, next gen "ERPs"?` 3. `Switching to Native AI ERP : "I swear accountants are the only reason some ERP systems still function."` Let's see if we can search for the text or comments inside `has anyone implemented campfire ERP before?` to see what the direct experiences are. Let's search for: `"currently onboarding to campfire and it has been an absolute disaster"` `"implemented campfire ERP before" "Accounting"` Let's search for specific comments or text from that thread. This will give us excellent grounds to write a balanced finding. While AI-native ERPs boast fast migrations, there are real-world practitioner pain points, bottlenecks, and "disasters" during onboarding. This is the exact kind of high-quality research that tells the story through concrete evidence! Let's search.

Ah, let's search for: `site:reddit.com/r/Accounting/comments/1r7f9v6/has_anyone_implemented_campfire_erp_before/` Or let's search specifically for quotes on Google from that thread. Let's search for: `"currently onboarding to campfire and it has been an absolute disaster"` `"We liked the" "campfire" "disaster"` `"implemented campfire ERP before" "We liked"` Let's see what comes up.

Okay, let's search specifically for the user `AdTasty154`'s posts or the text of `has anyone implemented campfire ERP before?` to see if we can get a bit more. Let's do a search for: `"AdTasty154" "campfire"` `site:reddit.com/user/AdTasty154` Let's see if we can read some of the snippet of their post. That would be very useful. Or we can do a broader search on Reddit for "campfire ERP" or "Rillet" or "DualEntry" to find comments about these next-gen ERPs and their onboarding. Let's run a search.

Ah! The web search budget is exhausted. No problem. We have a wealth of information from our previous searches and fetched pages, including: 1. The Rillet case study of OnlineMedEd migrating from NetSuite. 2. The Rand Group comparison of NetSuite vs Rillet (April 2026 update). 3. The LinkedIn Pulse article on Campfire ERP (March 2026/May 2026 context). 4. The DualEntry $90M Series A funding announcement (October 2025/2026 context) and its "NextDay Migration" engine. 5. The Reddit thread titles and descriptions showing that while AI ERPs are gaining massive traction, some users are experiencing "absolute disasters" during onboarding. Let's organize our findings. First, we should check if there are any existing notes on this topic, specifically related to the AI-native ERP market disruption. Let's see: the auto-injected relevant prior findings list includes: - "The Rise of AI-Native ERPs: Startup Challengers and Legacy Defensive Counter-Offensives" (slug: `ai-native-erp-market-disruption-2026`). Yes! We can update this finding or write a new one that directly answers the open thread: "How are AI-native ERPs automating historical data migration from legacy platforms?" Wait, let's look at the open thread title: "How are AI-native ERPs automating historical data migration from legacy platforms?" And let's look at the instructions. "For each finding worth persisting, call write_note. A finding TELLS THE STORY THROUGH CONCRETE EVIDENCE — it does not just describe the vibe. Every substantive finding must: - name and link the actual thing (the story, article, paper, or page that was posted/published) — not just 'the discussion', - carry 1-2 REPRESENTATIVE VERBATIM QUOTES, copied exactly, each kept with the link it came from (an HN comment permalink, the article URL, etc.), - then say what it means." Let's look at the details we gathered for DualEntry: - Source: [DualEntry Raises $90M Series A to Redefine ERP as AI-Native | DualEntry](https://www.dualentry.com/funding-announcement) - Verbatim Quotes: "DualEntry’s complete ERP accounting suite covers the full general ledger along with accounts receivable, accounts payable, live bank connections, audit controls, FP&A, and more." "The company’s NextDay Migration solution – powered by the world’s first ERP migration engine – eliminates agonizing implementation odysseys and gets teams live with its full accounting suite in 24 hours, migrating every line item, subledger, and attachment seamlessly and securely." "The funds will drive growth for DualEntry’s platform, which has already processed $100 billion worth of journal entries with AI automation, saved businesses thousands of hours on implementation and data migration, and signed thousands of global users – ranging from companies with $5 million in revenue to NYSE-listed businesses with hundreds of millions in ARR." Let's look at the details we gathered for Campfire: - Source: [Campfire ERP: The AI-First Revolution in Enterprise Finance](https://www.linkedin.com/pulse/campfire-erp-ai-first-revolution-enterprise-finance-landman-karny-s0kdc) - Verbatim Quotes: "Brian Ehrlich, Finance Director at Flex, implemented Campfire entirely in-house twice, closing books within three weeks of signing both times. This represents a significant improvement over traditional ERP implementations that often require 6+ months and extensive consultant involvement." "Flex reported saving over $300K in implementation costs and avoided hiring 1-2 full-time staff... Monthly close cycles reduced from 15 days to 3 days" "Campfire has demonstrated expertise in migrations from legacy systems, particularly Sage Intacct, with faster migration timelines compared to traditional 6+ month ERP implementations." Let's look at the details we gathered for Rillet: - Source: [NetSuite to Rillet: How OnlineMedEd Modernized Finance | Rillet Case Study](https://www.rillet.com/case-studies/netsuite-to-rillet-how-onlinemeded-simplified-reporting-and-modernized-their-ledger) - Verbatim Quotes: "With Rillet, we didn’t have to do anything—they handled everything, and the transition was seamless." - Dunia Gonzalez Aguero, OnlineMedEd's accounting manager. "The implementation process was long and painful, historical data was riddled with errors, and getting help from NetSuite’s support team often felt impossible... Rillet’s implementation team handled the entire migration process, ensuring all historical data was imported correctly from day one." Let's also look at the practitioner pushback / real-world bottlenecks: - Source: [has anyone implemented campfire ERP before? : r/Accounting](https://www.reddit.com/r/Accounting/comments/1r7f9v6/has_anyone_implemented_campfire_erp_before/) - Quote: "We are currently onboarding to campfire and it has been an absolute disaster." Let's write a comprehensive finding that addresses the open thread: "How are AI-native ERPs automating historical data migration from legacy platforms?" Wait, should we reuse the slug of the existing finding `ai-native-erp-market-disruption-2026` or pick a fresh slug? The instruction says: "When writing a finding that refines one of the above, reuse its slug to update. Otherwise pick a fresh slug." Since this directly refines the "Rise of AI-Native ERPs" topic by detailing the exact migration mechanics, tools (like DualEntry's NextDay Migration, Campfire's in-house implementations, Rillet's white-glove migration) and the real-world practitioner bottlenecks, we can reuse `ai-native-erp-market-disruption-2026` or we can write a fresh slug if we want it to be a separate note. Wait, let's search if there are other open threads or if we can resolve this thread. The thread is: `019e53e1-027e-7e6e-9690-28b181cf191b` Title: "How are AI-native ERPs automating historical data migration from legacy platforms?" Description: "While AI-native ERP startups like Campfire, Rillet, and DualEntry are winning migrations off SAP and NetSuite, what are the primary data migration and implementation bottlenecks for enterprises, and how are these startups using AI to automate the transfer and mapping of complex historical financial data?" Let's write a highly detailed, evidence-grounded finding. We will structure it beautifully, with the verbatim quotes, links, and real-world analysis. Let's double-check the rules: - No YAML frontmatter. - Title is the first `# ` heading. - Slug is passed as a parameter to `write_note`. - Carry 1-2 representative verbatim quotes, copied exactly, each kept with the link it came from. - End with a "## Sources" list. - Ground every finding in concrete evidence. Let's review the exact quotes and links to make sure they are flawless. First quote (DualEntry): "The company’s NextDay Migration solution – powered by the world’s first ERP migration engine – eliminates agonizing implementation odysseys and gets teams live with its full accounting suite in 24 hours, migrating every line item, subledger, and attachment seamlessly and securely." Source: [DualEntry Raises $90M Series A to Redefine ERP as AI-Native | DualEntry](https://www.dualentry.com/funding-announcement) Second quote (Campfire): "Brian Ehrlich, Finance Director at Flex, implemented Campfire entirely in-house twice, closing books within three weeks of signing both times. This represents a significant improvement over traditional ERP implementations that often require 6+ months and extensive consultant involvement." Source: [Campfire ERP: The AI-First Revolution in Enterprise Finance](https://www.linkedin.com/pulse/campfire-erp-ai-first-revolution-enterprise-finance-landman-karny-s0kdc) Third quote (Rillet): "With Rillet, we didn’t have to do anything—they handled everything, and the transition was seamless." Source: [NetSuite to Rillet: How OnlineMedEd Modernized Finance | Rillet Case Study](https://www.rillet.com/case-studies/netsuite-to-rillet-how-onlinemeded-simplified-reporting-and-modernized-their-ledger) Fourth quote (r/Accounting - Reddit): "We are currently onboarding to campfire and it has been an absolute disaster." Source: [has anyone implemented campfire ERP before? : r/Accounting](https://www.reddit.com/r/Accounting/comments/1r7f9v6/has_anyone_implemented_campfire_erp_before/) This is incredible because it presents both sides: the startups' marketing claims of 24-hour "NextDay Migration" and "white-glove" transitions, and the real-world practitioner friction ("absolute disaster" during onboarding). Let's write this note now. I will use the slug `ai-native-erp-migration-mechanics-and-bottlenecks-2026`. Or wait, does it refine `ai-native-erp-market-disruption-2026`? Yes, we can either update `ai-native-erp-market-disruption-2026` or write a new note with a fresh slug. Let's write a fresh slug `ai-native-erp-migration-mechanics-and-bottlenecks-2026` so we have a dedicated, deep-dive note on migration mechanics, and preserve the market-disruption note. Or wait, let's see if we should update the existing one. Actually, writing a fresh slug is better because the thread is specifically about migration and implementation bottlenecks, which is a highly technical and distinct sub-topic. Let's call `write_note`.

Great, the note is successfully written! Now, let's resolve the thread `019e53e1-027e-7e6e-9690-28b181cf191b` using the findings we just recorded. Let's see: `resolve_thread` requires `thread_id` and `cycle_id`, and takes an optional `resolution_note`. Let's do this. I'll state my intent and call `resolve_thread`.

The thread has been successfully resolved. Let's see if we should record any new threads. Are there any other open questions that a future cycle should pursue? We have researched: - AI-native ERP migration mechanics, automated mapping, and implementation bottlenecks. - The competitive dynamics of DualEntry, Campfire, and Rillet. - The SaaS rout, AI-native ERP disruption, vendor lock-in, and services ventures. Let's think. A high-value open question for a future cycle could be: "How are legacy mid-market and enterprise ERP vendors (like Oracle NetSuite with 'NetSuite Next' and SAP) pricing their AI capabilities, and are they shifting to consumption/value-based pricing models to counter the seat-compression threat from AI-native startups?" Yes! This is highly relevant to our topic brief which tracks "pricing model shifts," "legacy vendors losing contracts," and "what is changing for someone evaluating the enterprise software landscape." Let's record this new thread using `record_thread`. I will specify the title, kind, description, and cycle_id. Let's do it.

Great! The new thread has been successfully recorded. Now, let's call `finish_cycle` to complete this research cycle. I will state my intent first.

I have completed the research cycle on the enterprise software and services landscape, focusing on AI-native ERP migration mechanics and onboarding bottlenecks. I documented these findings in a comprehensive note and resolved the corresponding open question, while establishing a new thread to track how legacy ERP giants are adjusting their pricing models to counter seat compression.