How to migrate data from Quickbook desktop to ERPNext

ERPNext
1

Hi Frappe Family

I am working on one project Quickbook Desktop 23 software and i want to migrate data to erpnext so i am understanding how to do that manually export files and import to erpnext is it good approch or not if yes then when sales invoice or purchase invoices added and then payments of customer and vendors added then how clear status in sales and purchase invoices from unpaid to paid etc

if other person having other suggestions to successfully complete this project please guide me

2

Hi @alphaintelligence786

Please check documentation as following;

1 Like
3

Hi thanks for reply this is for online quickbook migration not for desktop based software i already explore it

4

For Desktop application, you have to use CSV uploaders for master and transactional records.

5

yes i use this tool data import tool but what if you have 10lack invoices, master data is not big problem main problem is invoices, like purchase, sales, journal entries, customer payment and vendors payments

2nd main issue quickbook is not erp system, it is very difficult to get all invoices of sales and purchase, journal entires so there are a lot of challanges i am facing

i just see only one solution to just add opening balance and sales invoices and purchase invoice just

do you have another solution if yes please tell me

6

You can export the data from the backed database engine used with quickbooks. Then accordingly you can import in ERPNEXT online.

7

Most of the times, it is not a good idea to import historic transactions from your legacy software.

Here are a few reasons why it might not be worth

  1. Different Inventory Valuation Systems: ERPNext uses Perpetual Inventory Valuation method which posts accounting transactions for every stock movement as opposed to Periodic Inventory valuation followed by most accounting packages including Quickbooks. So it is not an apples to apples comparison.
  2. Data structures will inherently be different: Chart of Accounts on ERPNext will tend to be much compact for the fact that it supports Accounting Dimensions. Due this mapping between two different data structures will be a huge task and you will realise that some imports will not work the way it should
  3. Importing Transactions is like Implementing the ERP before you test: If you think you can just take a dump from your legacy software and import it, you are mistaken. Discovery, Design and Configuration are important phases you might be skipping to set yourself up for success. It is like moving in to a new place with a new mind set, what got you here, won’t get you there! The way you enter transactions will change and should change drastically when you implement and move to an ERP system from a plain Accounting Software like Quickbooks.

What should you do instead, if having historic data is important for record keeping purposes

  1. Import only important snapshots of Financials: For example, import only closing balances of each Financial Year or Monthly depending on your volume of transactions. Be realistic with your expectations!

In general, redesign your Chart of Accounts well: Make sure you take advantage of Accounting Dimension and don’t overwhelm yourself of an Account/Ledger for every detail like Branch/Location/Department.

1 Like
8

I totally agree with @Manan_Shah. You can keep the older software as is, especially if it’s locally installed and doesn’t require any cost. Adding historic information is like bloatware. Try to navigate the customer away from this route.

9

I have developed a utility to fetch data from QuickBooks desktop and CSV/excel (all or any date range), using erpnext API, I will push data into erpnext (which is in progress). Definitely some data types, fields are required to be transformed. . I will share the utility soon…