Inside Insights · Season 3, Episode 53
Replacing RapidStart in Business Central: A Free Extension
A 30-minute migration estimate in Business Central has a way of turning into an afternoon once Excel workbooks and configuration packages get involved. Import Export PowerTool moves data with tab-delimited text files instead, writes to protected tables, and handles lot and serial numbers in item journal imports. This is a completely free app from Insight Works for Business Central. Hear how it changes opening balances, sandbox copies, and post-go-live cleanup.
In this episode
- Why RapidStart configuration packages struggle with large data loads
- How a plain text file skips custom fields Business Central doesn't have
- Opening inventory loads with lot and serial numbers
- Committing imports per table so earlier tables stay loaded
- Fixing protected records safely with permission sets
Read the transcript
Ryan: You know, usually when we talk about a medical diagnosis, there's this, this underlying expectation of precision.
Emma: Right? Yeah, it's very binary.
Ryan: Exactly. It's like engineering. You break your arm, the X ray shows that jagged white line on a black background and the doctor just points and says, you know, there it is, it's incredibly straightforward.
Emma: You get a clean answer. There's a defined problem and, well, a clear path to fix it.
Ryan: But if you, and I mean you, the listener, if you have ever been the person tasked with moving an entire company's historical data from an old system into a new enterprise resource planning system, Specifically Microsoft Dynamics 365, Business Central. You know that X ray machine is completely broken.
Emma: Oh, completely.
Ryan: It's not precise at all.
Emma: No, it's this landscape that is just murky and fragile and often wildly unpredictable. Like you think you know what you're moving and then the system just completely rejects it.
Ryan: Which is, I mean, the absolute definition of a high stakes bottleneck. We really have to remember that data isn't just some bottom byproduct of a business. It's the lifeblood of the modern enterprise.
Emma: Right.
Ryan: So when you're standing on the edge of a new system, go live. A failed data migration isn't just a, you know, a minor, it hiccup, it halts everything. It's a massive scheduling and financial problem. And that is exactly why today's deep dive is tailor made for you. Like if you're listening to this and you have ever felt that unique, very specific pain of watching a progress bar crawl at a snail's pace at like 2am on a Sunday, just praying it doesn't crash, Desperately hoping it doesn't crash before Monday morning. Yeah, this one is for you. Because our mission today is to decode exactly why large scale data migration is so often a complete nightmare.
Emma: And we're basing this on some really solid sources today too.
Ryan: We are, we're looking at actual technical documentation and product specifications really getting into the weeds. And more importantly, we are going to explore a specific totally free alternative that is quietly changing the game for developers and consultants.
Emma: It really is a game changer.
Ryan: Okay, let's unpack this. If you think about traditional data migration, it is essentially like trying to move an entire fully furnished house using only a fleet of unicycles.
Emma: A fleet of unicycles, wow.
Ryan: Right? I mean technically, yes, it is possible you could put a lamp on one unicycle, maybe like balance a chair on another one, but it is excruciatingly slow. It's incredibly fragile and you are almost certainly going to drop the couch.
Emma: That is a very apt, if slightly terrifying visual for how a lot of consultants feel on deployment weekends. But to understand why the default experience feels like writing a unicycle, we really have to look at the default tools provided.
Ryan: Okay.
Emma: In Business Central, the default mechanism for this is something called RapidStart Configuration Packages,
Ryan: which, honestly, that sounds incredibly fast.
Emma: I mean, it literally has the word rapid right there in the name.
Ryan: It does, yes.
Emma: But the reality of using RapidStart under the pressure of a massive data load is, well, it's brutal. When you really push it, the wheels start falling off those unicycles.
Ryan: Why is that?
Emma: Because we have to look at what RapidStart was actually architected to do, rather than what people try to force it to do. It was designed to reuse setup data.
Ryan: Okay, so like the foundation stuff.
Emma: Exactly. Imagine you're an implementation partner configuring a brand new company profile. You want to bring over the foundational rules. So the same tax codes, the same basic chart of accounts structure, payment terms, stuff like that. RapidStart is phenomenal for that because it's small. Right. You are moving a few dozen, maybe a few hundred highly structured rows of logic. But what's fascinating here is, is that it was absolutely not built to handle high volumes of unstructured transaction records.
Ryan: So it's great for building the shelves, but it's terrible for stocking them with like, tens of thousands of individual items.
Emma: Precisely. When we're talking about pushing through thousands of inventory items, endless lists of contacts, or massive historical ledger records. That is where the architecture of RapidStart begins to work against you.
Ryan: Because the friction is just baked into how it operates.
Emma: Right.
Ryan: I was reading the SPECs, and a RapidStart configuration package forces you to create a separate Excel spreadsheet for every single table you want to touch.
Emma: Every single one?
Ryan: Yes. And not only that, every single field has to be strictly defined and mapped to the package before you can even attempt to import it. Which I have to pause here because I'm really struggling with the design logic behind this.
Emma: It can feel very backwards.
Ryan: Right. Because if Microsoft knows that literally every single business migrating from a legacy system is going to have custom fields, like weird data points that made sense in their old software but don't exist in Business Central, why force the consultant to map every single one beforehand?
Emma: It's a fair question.
Ryan: Why can't the system just look at the data, take what it needs and ignore the rest? Isn't that just Creating endless busywork for the people doing the job.
Emma: I completely understand why it feels like endless busywork, but it's actually a reflection of how rigid relational database structures work. They prioritize safety over speed.
Ryan: Safety.
Emma: Okay. Business Central is an enterprise resource planning system. It needs absolute certainty about where a piece of data belongs so it doesn't corrupt the financial ledger.
Ryan: Ah, I see.
Emma: So RapidStart forces you to map everything so the SQL database underneath knows exactly what it is swallowing. It's an enforcement of data integrity.
Ryan: So it's basically forcing you to be meticulous.
Emma: Yes, but as you noted, when a consultant is doing a bulk migration, they encounter all those custom fields. And RapidStart has no simple mechanism to just, you know, ignore an unmapped column in an Excel sheet.
Ryan: It just freaks out.
Emma: Basically, yes. If the schema doesn't perfectly match, the package trips over itself, it generates an error and stops. It's safe. Sure. But it is incredibly problematic when you're trying to move thousands of rows of messy historical data that you haven't perfectly sanitized yet.
Ryan: Which brings us to how the markets solve this problem. Because if RapidStart is that fleet of unicycles and safe for small trips, but unwieldy for moving a whole house, then the alternative we're looking at today is the moving truck.
Emma: Yes. The Import Export PowerTool.
Ryan: Right. It's a free app from Insight Works, and it represents a totally different architectural approach. And the craziest part to me is how it handles the files themselves. Like we just talked about, how RapidStart generates this tangled, fragile web of Excel sheets. The PowerTool completely ditches Excel entirely. It uses one plain text file to handle multiple tables.
Emma: It does. And from one single setup page, a user can execute four core operations. They can export, import, update, and delete.
Ryan: That's it. Just one page?
Emma: Just one page. And it even has backward compatibility, so it can take an existing RapidStart package and use it as an export template.
Ryan: Oh, wow.
Emma: Yeah. Meaning if a consultant already spent hours building a package schema, they don't lose that foundational work, they just execute it through a vastly more efficient engine.
Ryan: Okay, I need you to explain this plain text aspect to me, because this is where I get completely lost.
Emma: Sure.
Ryan: Ditching Excel spreadsheets for plain text. I mean, we are in an era of cloud computing, AI, incredibly complex data visualization. Going back to a raw text file sounds like trading a smartphone for a telegraph.
Emma: It really does sound like a downgrade.
Ryan: Right. I need you to explain how losing the structure of an Excel sheet doesn't just result in a chaotic data dump. Like how is downgrading the file type an upgrade in performance?
Emma: It sounds totally counterintuitive until you look at the physics of how software parses files. Think about what an Excel file really is under the hood. Okay, it isn't just data. It is an incredibly heavy XML structure. It carries formatting, fonts, colors, cell borders, formula evaluation, logic, hidden metadata.
Ryan: Oh, right, all the visual stuff.
Emma: Exactly. When a system tries to push tens of thousands of records from an Excel file into a database, the processor has to read and render all of that extraneous information just to find the actual text you care about.
Ryan: So it's spending CPU cycles reading the fact that a cell is like, painted yellow, even though the database doesn't care about the color yellow at all.
Emma: Precisely. All of that extra overhead acts like drag on an airplane. A plain text file, on the other hand, like a CSV or, strips all of that away.
Ryan: It's just the data.
Emma: It is raw, unadulterated data, just values separated by commas. It allows for blinding speed because the computer is only processing the actual payload, not the packaging.
Ryan: Okay, that makes sense for the speed, but what about that rigid mapping we talked about? How does a plaintext file magically solve the custom field problem that RapidStart chokes on?
Emma: Because of how the PowerTool's parser is engineered, when the tool reads the text file, it loads the target table schema into temporary memory. It looks at the first line of your text file, the header row. If it sees a column header in the text file that does not exist in the Business Central schema, it dynamically instructs the import stream to just skip the byte offset for that specific column on every single subsequent row.
Ryan: Wait, really? So it practically says, I see you have a column for legacy customer rating. I don't have a place for that, so I'm just going to ignore it and keep moving.
Emma: Exactly. The rigid mapping requirement is bypassed dynamically in memory. You just push the data and the parser takes what fits and ignores the rest.
Ryan: That's wild.
Emma: It doesn't throw an error, doesn't halt the import. This makes moving messy legacy data incredibly practical, because you don't have to spend hours scrubbing every custom column out of your source file before you even try to import it.
Ryan: And we know the speed difference is not just theoretical. I mean, looking at the technical documentation, we've seen real world scenarios that completely reframe what a data load looks like.
Emma: The benchmarks are crazy.
Ryan: They really are. Consider this review From a consultant, Michael Inga. He had to load over 20,000 inventory items into a new environment using the traditional RapidStart configuration packages. That specific load took over an hour of processing time.
Emma: Over an hour of just sitting and waiting.
Ryan: Right. And like we said, hoping it doesn't fail at minute 59. But by pivoting to this plaintext PowerTool, those same 20,000 inventory items were imported in under one minute.
Emma: Under a minute for 20,000 items is just a staggering performance leap.
Ryan: Going from over an hour to under a minute completely changes the math on a deployment weekend. If you are an IT director listening to this, that is the difference between your team sleeping in their own beds and or sleeping under their desks.
Emma: It changes the entire rhythm and stress level of the project. And there are specific, highly complex tasks where this processing speed really shines.
Ryan: Like what?
Emma: Opening inventory loads. For example, when you're loading starting stock, the PowerTool automatically creates lot and serial number entries on item journal imports.
Ryan: Which is usually a massive headache. Right. Because tracking those numbers requires touching multiple interconnected tables simultaneously, it is notoriously difficult.
Emma: But the tool handles the background creation automatically, so the tracking is perfectly in place from day one. It's also exceptional for environment management.
Ryan: Like moving between sandbox and production.
Emma: Yes, exactly. Moving data between a sandbox testing environment and a production environment. Or even copying pristine setup data between different companies within the same tenant. You just use that same lightweight text file as the vehicle. It handles all your dimensions seamlessly, shortcut, non shortcut default. And it successfully carries over record links and notes.
Ryan: Oh, that feels huge. So the actual qualitative history attached to a customer, like the notes about their preferences or past issues that comes along for the ride.
Emma: Historical context is often what operations teams fear losing the most during a digital transformation. Preserving those notes keeps the human element of the data intact.
Ryan: Here's where it gets really interesting though. Let's shift gears to a feature that I think is the real unsung hero of this tool. It's called commits per table.
Emma: Yes.
Ryan: From what I understand in the specs, if you have a massive multi table text file and an error occurs late in the process, you don't need a full restart because the earlier tables stay loaded in the database.
Emma: That's right.
Ryan: I liken this to hitting a save point in a video game right before a boss fight. You don't have to start the whole level over. But I need you to break down the mechanics of this. Why is a failure in traditional systems so catastrophic? And how does this save point actually save a consultant time in the real world.
Emma: To understand the pain of a traditional failure, we have to talk about database atomicity. Modern relational databases generally operate on an all or nothing principle for batch jobs.
Ryan: Okay.
Emma: This is called acid compliance. If you send a batch of data involving tables A, B, C and D and the system hits a fatal error on table D, the database panics. It assumes that if table D failed, tables A, B and C might now be orphaned or logically invalid.
Ryan: Oh, I see.
Emma: So to protect its own integrity, the system triggers a cascading rollback. It deletes everything it just successfully imported from A, B and C. So it
Ryan: actively punishes you for a failure by wiping out your successes?
Emma: Essentially, yes. It is protecting the ledger, but it is devastating for the person running the migration because then the consultant has to untangle this massive web, figure out exactly which row in table D caused the crash, fix the formatting, and start the entire hour long import process over from absolute zero.
Ryan: Just brutal.
Emma: And they just have to pray it doesn't fail on table E. So how
Ryan: does commits per table bypass that atomicity problem without corrupting the database?
Emma: By breaking the batch into smaller isolated transactions. The tool effectively puts a firewall between the tables and tells the database, here is table A. Validate it. Okay, it's good. Commit it permanently. Now here is table B. Oh, wow. Right. So if table D fails, the system only rolls back table D. Tables A, B and C are already locked in. The consultant only has to deal with the specific localized data that caused the problem. It turns a catastrophic hours long failure into a minor 5 minute speed bump.
Ryan: Okay, so we've established it is incredibly fast and resilient for moving data into the system, but let's pivot because the reality of ERP management is that sometimes the data already inside the system is just completely broken.
Emma: Very true.
Ryan: We're moving from looking at this as a bulk migration tool to looking at it as a highly surgical repair tool.
Emma: And this is where the capabilities get very serious and frankly, very powerful. The PowerTool can reach protected tables,
Ryan: which is wild to think about. We are talking about item ledger entries, customer ledger entries, general ledger entries. The foundational immutable accounting records of the system.
Emma: The core.
Ryan: Right, and this tool allows a user to edit fields that Business Central explicitly marks as read only. Now hold on. I am definitely alarmed by this. I need you to talk me off a ledge here.
Emma: I get it, I get it.
Ryan: Editing protected read only ledger entries directly. That sounds like giving someone the nuclear launch codes just because they need to change a light bulb in the silo. Changing a ledger directly is an auditor's worst nightmare. Isn't this an credible liability for production data?
Emma: This raises an important question. And it's the exact right question to ask any IT director or financial controller hearing read only ledger editing is going to immediately raise a red flag if they should. Yes, in a double entry accounting system, you aren't supposed to change history. You are supposed to post a reversing entry to correct a mistake. Giving unrestricted restricted write access to the ledger is a recipe for a failed audit or worse, massive data corruption.
Ryan: Exactly.
Emma: But there are times when system junk like a corrupted lingering reservation entry is actively blocking a crucial environment upgrade. You can't reverse it because the system logic is caught in a loop. Usually you have to halt your entire project and hire a developer to write a custom one off extension just to bypass the user interface lock and delete the bad record.
Ryan: Which takes days and costs thousands of dollars.
Emma: Exactly. The PowerTool allows a consultant to filter down to that specific corrupted record, preview it, and apply a surgical update or deletion directly. But to address your alarm, it is built with incredibly strict safety rails. It is not a backdoor.
Ryan: Okay, walk me through those rails.
Emma: First and foremost, it relies entirely on the user's existing permissions.
Ryan: So if I can't access the ledger normally, the tool won't magically let me do it.
Emma: Correct. It manages this through two distinct permission sets. There's a manager set which is heavily restricted. This grants access to edit the setup page, reach those protected tables, and even disable system change logs for massive speed boosts during imports.
Ryan: Got it.
Emma: And then there's a standard user set which absolutely cannot change those settings or touch protected tables. You only give the manager permissions to the people who fundamentally understand the physics of Business Central data structures.
Ryan: Okay, so the human element is the first safeguard. But what if a manager makes a mistake? What if they try to delete something they shouldn't?
Emma: That is the second and more important layer of protection. Business Central's core business logic validations still apply. The PowerTool bypasses the user interface lock, sure, but it does not bypass the relational database rules.
Ryan: Okay, I think I see where this is going.
Emma: If a manager tries to delete a ledger entry that other vital records depend on, say, trying to delete an item that still has open inventory quantities, the system logic catches the dependency and blocks the action. The file will just fail to import. It will not force its way in and break the fundamental laws of the software.
Ryan: Ah, that makes me feel much better. The database is still defending itself. So we have established that this is a powerhouse. It's fast, it skips the busy work dynamically, it saves your progress table by table, and it allows for safe surgical fixes. Yes, but to really ground this deep dive, we need to set some firm boundaries. Listeners need to know exactly what this tool is and what it isn't, because a common trap in it is finding a great tool and trying to use it for literally everything.
Emma: That is a crucial distinction to make. We have to clearly separate a migration tool from an integration tool. As Mark Hamblin, a senior solution advisor at Insight Works, puts it in the product specs, it is basically a data migration tool. It's not an integration tool, and it's not going to replace the cloud migration tool from Microsoft.
Ryan: Right? A migration tool moves data from point A to point B. It's a discrete event. An integration tool is designed to constantly, seamlessly synchronize data between two live systems in real time. So if you were listening to this and hoping this free tool is going to automatically sync your Shopify e commerce website with Business Central every five minutes, this isn't it.
Emma: Correct out of the box. It requires a human to hit the button. It cannot run imports on a scheduled timer. On its own.
Ryan: Get it out.
Emma: However, for the technical folks listening, it does publish events and callable functions. This means a partner could easily build a very small custom extension to utilize the PowerTool's engine for scheduled background imports. But inherently on its own, it is an ad hoc tool.
Ryan: And we absolutely need to reiterate the cost structure here, because in the world of enterprise ERP software, this feels almost unheard of. It is 100% free, completely free. There is no user limit. There are no hidden premium tiers. It works across essential premium and team member licenses, and it is globally available
Emma: for Business Central online, which is highly unusual. Tools with this level of deep system access and parsing capability usually come with a significant subscription fee.
Ryan: So what does this all mean? Like connecting this directly to you, the listener if you are prepping for a massive ERP upgrade, or maybe you inherited a sandbox environment that is just a total mess of bad test data. This fundamentally changes your toolkit.
Emma: Absolutely.
Ryan: You don't have to rely entirely on the fragile unicycle style crawl of configuration packages. And you don't have to halt your project to wait for a developer to write a custom script every single time you encounter a stubborn read only error.
Emma: What we're really witnessing here is the democratization of data management. This tool takes capabilities that previously required a dedicated, highly specialized Developer writing AL code and puts them directly into the hands of the consultants, the integrators and the IT managers who are actually doing the day to day deployment work. It removes the middleman for these critical high volume tasks.
Ryan: It's a massive shift in how we approach deployments. I mean, we started this journey looking at the rigid world of RapidStart, where every single field demands a predefined schema and a heavy Excel sheet.
Emma: Right?
Ryan: And we've explored the mechanics of moving to the fast dynamic raw text parsing of the Import Export PowerTool. We've broken down how. Understanding these back end mechanics, knowing how a text parser skips custom fields, knowing why committing per table saves you from cascading database rollbacks, and knowing how you can safely surgically edit read only tables without breaking business logic can literally save you days of frustration during a high stakes tech deployment.
Emma: And if we connect this to the bigger picture, we really have to ask ourselves how tools like this change our fundamental psychological relationship with historical information.
Ryan: What do you mean?
Emma: Well, for decades, legacy data has been viewed by corporate leadership as this heavy immovable burden. It's viewed as a massive liability that dictates and severely limits your future software choices. Companies stay on bad software because they are just terrified of the migration, right?
Ryan: The data feels like concrete.
Emma: Exactly. But if we can bypass the traditional developer bottlenecks, if a simple raw text file can instantly update, delete, or safely migrate tens of thousands of records in less than a minute, what if we started viewing all business data as totally fluid?
Ryan: Oh, I like that.
Emma: What if your historical data isn't a burden, but something easily moldable, ready to be completely reshaped, scrubbed and moved at a moment's notice to fit wherever the business needs to go next? When the fear of moving data disappears, a company's agility just skyrockets.
Ryan: That is a brilliant way to frame it. Moving from seeing your digital footprint as a heavy anchor to seeing it as a fluid asset that you have complete control over, it completely changes the conversation in the boardroom.
Emma: It really does.
Ryan: Well, that brings us to the end of our dive today. Thank you for joining us on this exploration of data migration and for digging into the hidden underlying mechanics that actually make it work. Keep questioning the tools you're handed, keep looking for those elegant plaintext solutions in an overly formatted world, and we will catch you on the next deep dive.
More episodes
- S3 E48 · 22 minBusiness Central gets 10 free apps from Insight WorksBarcode Generator PowerTool · DocXtender · Enhanced Forecasting Worksheet · Enhanced Planning Worksheet · Graphical Scheduler · Import Export PowerTool · Order Ship Express · PrintNode Connector PowerTool · Safety Logbook · WMS ExpressOctober 14, 2026
- S3 E35 · 26 minHow VIPA Hellas unified warehouse ops in Business CentralAdvanced Inventory Count · Barcode Generator PowerTool · Import Export PowerTool · PrintNode Connector PowerTool · Warehouse InsightJune 30, 2026