If you are planning a QuickBooks Enterprise to Online migration and are worried that years of invoices, payments, journal entries, customer balances, or QuickBooks Enterprise historical data will disappear, stop before starting the conversion.
The short answer is: not every QuickBooks Enterprise record transfers to QuickBooks Online in exactly the same form. Many lists and transactions can migrate, but some fields, workflows, reports, links, and Desktop-specific features change or do not transfer. Intuit’s current documentation specifically identifies data that moves, data that changes, and data that does not move during the transition from QuickBooks Desktop to QuickBooks Online.
That is why users sometimes report QuickBooks Enterprise missing transactions, QuickBooks Online missing historical data, or unexpected QuickBooks Online migration errors immediately after conversion.
If your accounting records are business-critical, do not treat the migration like a simple software installation.
Treat it like a data conversion project.
This guide explains what happens to historical data, why records may appear different after migration, how to troubleshoot QuickBooks Enterprise migration problems, and what to do if QuickBooks Enterprise data is not transferred as expected.
What Happens to QuickBooks Enterprise Historical Data After Migration?
The first thing to understand is that moving from QuickBooks Enterprise to QuickBooks Online does not necessarily create a perfect one-to-one copy of your Desktop company file.
QuickBooks Desktop and QuickBooks Online use different platforms and have different features.
During a QuickBooks Enterprise data migration, some information can transfer directly, some information is converted into a different format, and some Desktop-specific information does not transfer.
In practical terms:
- Customers and vendors can transfer, but certain fields may not.
- Chart of Accounts can transfer, but account details may be adjusted for QuickBooks Online.
- Invoices, bills, checks, deposits, expenses, estimates, and other transactions can migrate, subject to the applicable migration process and limitations.
- General journal entries can migrate, but certain Desktop-specific characteristics may not.
- Some reports and report configurations do not transfer.
- Some scheduled transactions and reminders do not transfer.
- Certain inventory information and Desktop-specific fields may not transfer.
- Reconciliation information and historical reports can behave differently after migration.
So if you are asking:
“Do all QuickBooks Enterprise transactions transfer to QuickBooks Online?”
The safest answer is:
No. Do not assume every transaction, field, link, report, or Desktop feature will transfer identically.
That is the central issue behind many QuickBooks Enterprise conversion errors.
What Causes This QuickBooks Issue?
If your QuickBooks Enterprise to Online migration resulted in missing historical records or changed transactions, there are several possible causes.
1. Desktop and Online Handle Data Differently
QuickBooks Enterprise is a Desktop product with functionality that does not have a one-to-one equivalent in QuickBooks Online.
When the data is converted, QuickBooks Online has to map Desktop information into its own structures.
That can change:
- Account classifications
- Customer/job structures
- Inventory fields
- Transaction fields
- Report behavior
- Reconciliation information
- Recurring transactions
- Custom fields
- Workflow settings
Intuit specifically notes that some QuickBooks Desktop features are unavailable in QuickBooks Online and provides a detailed list of what moves and what does not.
2. QuickBooks Enterprise Historical Data May Not Look the Same
A transaction can technically migrate while appearing different.
For example, customer jobs in Desktop can be represented differently in QuickBooks Online.
Intuit states that leaf-node jobs can migrate as projects while other jobs can migrate as sub-customers.
Therefore, a user may search for an old customer or job using the exact Desktop structure and conclude:
“My QuickBooks Enterprise data is missing.”
The data may instead have been converted into a different Online structure.
3. Some Desktop Fields Do Not Transfer
One of the most common sources of confusion is that a transaction can transfer while some associated fields do not.
Intuit’s migration documentation identifies multiple Desktop fields and features that don’t move to QuickBooks Online. Examples include certain customer/vendor fields, custom fields, reminders, scheduled transactions, and specific transaction attributes.
This creates a classic QuickBooks Enterprise migration problem:
The transaction exists, but information attached to the transaction does not.
That is different from the transaction itself being lost.
4. Journal Entries Can Change
Users searching for:
“QuickBooks Enterprise general journal entries not transferred to Online”
should pay particular attention to journal-entry mapping.
QuickBooks Online supports importing journal entries, and Intuit’s current import documentation lists Journal Entries among the transaction types that can be imported.
However, not every Desktop-specific characteristic necessarily survives.
For example, Intuit’s Desktop-to-Online migration documentation identifies billable statuses for journal entries as an item that does not move.
So before declaring that your QuickBooks Enterprise general journal transactions are missing, compare:
- Transaction date
- Journal entry number
- Accounts
- Debit amounts
- Credit amounts
- Memo
- Customer/job association
- Class
- Billable status
- Related reporting
5. Your Company File May Be Too Large or Complex
Large Enterprise files can create migration complications.
Intuit currently documents a 4,000,000-target limit for QuickBooks Desktop Enterprise 2022 and newer when preparing a Desktop file for import to QuickBooks Online.
This is important because:
File size in MB is not the only measurement that matters.
QuickBooks uses the concept of targets when evaluating the file for migration.
If your Enterprise file is extremely large, you may need to reduce its size before migration.
6. Condensing Can Change Historical Reporting
If you use the QuickBooks Desktop Condense Data utility to prepare the file for migration, understand what you are doing before you start.
Intuit says that for QuickBooks 2019 and newer, condensing reduces overall file size while saving the data, but reports may not match after condensing. Intuit also recommends maintaining a backup of the original company file.
That means:
Never treat a condensed file as your only historical archive.
Keep the original, unmodified Desktop backup.
How to Fix QuickBooks Enterprise Migration Errors — Step-by-Step
If you already completed the migration and now have a QuickBooks Enterprise issue, use the following troubleshooting sequence.
Step 1: Stop Making Changes
Quick Fix
If historical transactions appear missing:
Stop entering new transactions until you understand the discrepancy.
Do not attempt to recreate hundreds of missing invoices or journal entries manually.
First determine whether the records:
- Failed to migrate.
- Migrated under a different structure.
- Are being filtered out of the current report.
- Were converted into another transaction type.
- Are outside the migration scope.
- Are present but missing specific fields.
This simple step can prevent duplicate accounting records.
Step 2: Preserve Your Original Enterprise File
Before performing advanced QuickBooks troubleshooting, create and preserve a complete backup of the original QuickBooks Enterprise company file.
Your original Desktop file should be treated as a historical reference point.
Intuit’s current guidance recommends creating a local backup before condensing or performing data-transfer operations.
Keep:
- Original Enterprise company file
- Verified backup
- Migration date
- QuickBooks Online company details
- Migration reports
- Any error messages
- Screenshots of discrepancies
- Accountant’s reports from before migration
This gives you a reliable baseline for reconciliation.
Step 3: Compare the Balance Sheet
Quick Fix
Run the same reporting period in both systems.
Compare:
- Total assets
- Total liabilities
- Equity
- Income
- Expenses
- Accounts receivable
- Accounts payable
- Bank accounts
- Credit cards
- Inventory
- Retained earnings
Do not start by comparing individual transactions.
Start with the financial statements.
If the balance sheet does not agree, you have a larger migration discrepancy that needs investigation.
Step 4: Compare the Profit and Loss
Run a Profit and Loss report in QuickBooks Enterprise for the same date range used during migration.
Then run the corresponding report in QuickBooks Online.
Compare:
- Total income
- Cost of goods sold
- Operating expenses
- Other income
- Other expenses
- Net income
If the totals differ, drill down into the accounts.
This helps identify whether the problem is:
- Missing transactions
- Changed account mapping
- Date differences
- Transaction classification
- Inventory conversion
- Journal-entry differences
Step 5: Investigate QuickBooks Enterprise Missing Transactions
If you are specifically facing:
“Why are my QuickBooks Enterprise transactions missing after migration?”
do not immediately assume the transactions were deleted.
Check the following.
Search by:
- Customer
- Vendor
- Transaction number
- Date
- Amount
- Account
- Memo
- Transaction type
Then compare the result against the original Enterprise file.
Check transaction types separately
Create separate comparisons for:
- Invoices
- Payments
- Bills
- Bill payments
- Checks
- Deposits
- Expenses
- Sales receipts
- Estimates
- Purchase orders
- Journal entries
This makes a large discrepancy much easier to isolate.
Step 6: Investigate General Journal Entries
If your biggest concern is:
“QuickBooks Enterprise general journal entries not transferred to Online”
perform a dedicated journal-entry comparison.
In the original Enterprise file, document:
- Date
- Entry number
- Debit account
- Credit account
- Amount
- Memo
- Class
- Name/customer
- Billable status
- Other relevant fields
Then compare those records with QuickBooks Online.
Remember that QuickBooks Online supports journal-entry import, but Desktop-specific information can change during migration. Intuit specifically identifies billable status as an attribute that does not move with journal entries during Desktop-to-Online migration.
Step 7: Check Customers and Jobs
A major source of QuickBooks Online missing historical data complaints is customer/job structure.
QuickBooks Desktop and QuickBooks Online don’t organize these relationships identically.
Intuit states that:
- Leaf-node jobs can migrate as projects.
- Other jobs can migrate as sub-customers.
Therefore, search for the customer under:
- Customer list
- Projects
- Sub-customers
- Parent customer
Do not assume a missing job name means its financial history disappeared.
Step 8: Check Reports That Do Not Transfer
If your historical data appears correct but an old report is missing, the issue may not be transaction loss.
Some Desktop reports do not transfer.
Intuit’s current migration documentation states that the Audit Trail and Memorized Reports do not move to QuickBooks Online.
Therefore:
Missing report ≠ missing accounting transaction.
This distinction is critical.
If a business needs historical Desktop-only reporting, retain access to the original Enterprise environment and archive the reports before migration.
Step 9: Review Reconciliation History
Bank reconciliation is another area that deserves special attention.
Your transactions may transfer while historical reconciliation reporting does not.
Intuit identifies past reconciliation reports among the information that does not move to QuickBooks Online.
After migration, verify:
- Beginning balances
- Ending balances
- Cleared transactions
- Reconciled transactions
- Outstanding checks
- Outstanding deposits
- Credit card balances
- Bank account balances
If the numbers don’t match, stop and investigate before performing another reconciliation.
Step 10: Check Inventory
Inventory-heavy businesses should be especially careful with a QuickBooks Enterprise to Online conversion.
Enterprise users often rely on advanced inventory workflows, multiple locations, assemblies, custom item fields, and other Desktop functionality.
Not every Desktop inventory field transfers.
Intuit specifically lists certain inventory and non-inventory item fields that do not move to QuickBooks Online.
Before completing the migration, compare:
- Quantity on hand
- Inventory asset balance
- Average cost
- Item names
- SKU information
- Sales price
- Purchase cost
- Inventory valuation
- COGS
- Open purchase orders
- Assemblies
- Inventory locations
For an inventory-heavy Enterprise company, professional migration testing is strongly recommended.
Advanced Fix: Prepare the Enterprise File Before Migration
If you have QuickBooks Enterprise migration problems before the conversion, preparation can prevent many issues.
1. Create a Full Backup
Keep the original file untouched.
2. Verify the Company File
Run available Desktop data verification tools and resolve serious data integrity warnings before migration.
3. Remove Unnecessary Data Carefully
Unused list entries and unnecessary historical data can contribute to a large file.
However, do not delete historical transactions simply to make migration easier without understanding the accounting consequences.
4. Check File Size and Targets
For applicable Enterprise versions, Intuit currently documents a 4,000,000-target ceiling for the Desktop file when preparing it for QuickBooks Online.
5. Consider Condensing Only When Appropriate
Intuit recommends preparing a backup and explains that condensing can affect reports.
If your company requires detailed historical reporting, do not condense blindly.
Quick Fix Methods for US Users
If you need a fast answer to a QuickBooks Enterprise conversion error, use this checklist.
Quick Fix Checklist
1. Don’t delete the Enterprise file.
Keep the original as your historical archive.
2. Don’t recreate missing transactions immediately.
Confirm whether they actually failed to migrate.
3. Compare the Balance Sheet first.
This quickly shows whether the migration changed the financial position.
4. Compare the Profit and Loss.
Look for account-level differences.
5. Search by transaction number.
This is often faster than searching by customer name.
6. Check customer/job conversion.
A Desktop job may appear as a project or sub-customer in Online.
7. Review journal entries separately.
Do not assume a missing field means a missing journal entry.
8. Check reports separately from transactions.
Some Desktop reports do not transfer.
9. Review reconciliation data.
Past reconciliation reports may not migrate.
10. Verify inventory independently.
Inventory discrepancies can have a major financial impact.
QuickBooks Enterprise to Online Migration: What Data Transfers?
Here is a practical overview.
| Data Category | Migration Consideration |
|---|---|
| Chart of Accounts | Generally transfers, but account structures can change |
| Customers | Transfers, but some Desktop fields may not |
| Jobs | Can convert into projects/sub-customers |
| Vendors | Transfers, but certain fields may not |
| Employees | Can transfer, with specific payroll/data considerations |
| Invoices | Can transfer, but certain fields/features may change |
| Bills | Can transfer, subject to Online plan/import rules |
| Checks | Can transfer |
| Deposits | Can transfer |
| Expenses | Can transfer |
| Estimates | Can transfer, but status/link behavior may change |
| Journal Entries | Can transfer, but some Desktop attributes may not |
| Purchase Orders | Can transfer, but relationships can change |
| Inventory | Requires careful validation |
| Audit Trail | Does not transfer |
| Memorized Reports | Does not transfer |
| Past reconciliation reports | Do not transfer |
| Scheduled transactions | May not transfer |
| Reminders | Do not transfer |
Intuit’s current Desktop-to-Online documentation should be treated as the authoritative checklist for the exact product and migration path being used.
QuickBooks Enterprise Diamond to Online: What Should You Check?
Businesses searching for QuickBooks Enterprise Diamond to Online migration should be particularly cautious.
Enterprise environments can contain:
- Large customer lists
- Large item lists
- Advanced inventory
- Multiple users
- Classes
- Locations
- Custom workflows
- Extensive transaction history
- Specialized reports
- Third-party integrations
The question should not simply be:
“Can my Enterprise file migrate?”
The better question is:
“Will the resulting QuickBooks Online company support the accounting workflows my business actually uses?”
Before migration, create a feature inventory.
Document:
- Accounting workflow
- Inventory workflow
- Payroll workflow
- Sales process
- Purchasing process
- Reporting requirements
- Bank feeds
- Payment processing
- Third-party integrations
- User permissions
- Custom fields
- Recurring transactions
- Historical reporting requirements
Then map each feature to QuickBooks Online.
QuickBooks Enterprise Migration 793 Errors and Other Conversion Errors
If you encounter a QuickBooks Enterprise migration 793 error, or another migration-specific error code, do not guess at the cause based only on the number.
Document:
- Exact error code
- Complete error message
- QuickBooks Enterprise version
- Operating system
- Company-file size
- Number of users
- Whether the error occurs during preparation or upload
- Whether the same error occurs with a test file
- Whether the file was condensed
- Whether third-party integrations are involved
Advanced troubleshooting process
- Back up the original Enterprise company.
- Preserve the error screenshot.
- Update the applicable Desktop software where appropriate.
- Verify the company file.
- Review migration requirements.
- Check the file’s target count if applicable.
- Test the migration with a controlled copy.
- Identify the transaction/list category causing the failure.
- Correct the underlying data issue.
- Retry the migration only after preserving the previous state.
Avoid repeatedly uploading the same problematic file without identifying the cause.
How to Transfer Historical QuickBooks Enterprise Data to QuickBooks Online
If your goal is:
“How do I migrate QuickBooks Enterprise to Online without losing historical data?”
use this workflow.
Before Migration
Step 1: Back Up
Create a complete backup of the Enterprise company file.
Step 2: Document Your Financial Position
Save:
- Balance Sheet
- Profit and Loss
- Trial Balance
- A/R Aging
- A/P Aging
- Inventory Valuation
- Bank balances
- Credit card balances
- Key general ledger reports
Step 3: Export Critical Reports
Save reports that your business may need later, particularly Desktop-specific reports.
Step 4: Identify Non-Transferable Features
Use Intuit’s Desktop-to-Online transfer documentation to identify what does not move.
Step 5: Prepare QuickBooks Online
Make sure the correct subscription and company setup are ready.
Step 6: Perform the Migration
Use the supported migration/import workflow applicable to your QuickBooks Enterprise version and QuickBooks Online subscription.
Step 7: Validate
Do not stop after the migration completes.
Validate the books.
After Migration: The 10-Minute QuickBooks Troubleshooting Audit
Immediately after QuickBooks Enterprise to Online migration, check these items.
1. Balance Sheet
Does the ending balance match?
2. Profit and Loss
Does net income match for the selected period?
3. Accounts Receivable
Compare:
- Total A/R
- Customer balances
- Old invoices
- Payments
- Credits
4. Accounts Payable
Compare:
- Total A/P
- Vendor balances
- Open bills
- Bill payments
- Credits
5. Bank Accounts
Compare:
- Book balance
- Cleared balance
- Outstanding items
6. Credit Cards
Verify the balance and outstanding transactions.
7. Inventory
Compare quantity, valuation, and COGS.
8. Journal Entries
Search for major year-end and adjusting entries.
9. Historical Reports
Confirm that critical reports are available or archived separately.
10. Tax and Year-End Data
Compare the final Desktop reports against the Online reports before relying on the migrated data for tax or financial reporting.
QuickBooks Enterprise Year-End Journal Entries After Migration
Year-end adjustments deserve special attention.
If your accountant posted:
- Depreciation
- Accruals
- Prepaid expenses
- Payroll adjustments
- Tax adjustments
- Retained earnings adjustments
- Inventory adjustments
- Closing entries
in QuickBooks Enterprise, identify those entries before and after migration.
Create a dedicated reconciliation list.
Why?
A company can have the correct overall balance while a particular journal-entry attribute has changed.
For example, a journal entry may still affect the correct accounts and amounts while losing a Desktop-specific property.
Therefore, compare the accounting effect, not just the visual appearance.
Why QuickBooks Enterprise Data Is Not Transferred Exactly as Expected
There are three different scenarios.
Scenario 1: The Transaction Transferred
The transaction exists in QuickBooks Online.
But:
- The name changed.
- The job structure changed.
- A field disappeared.
- A status changed.
- A link changed.
This is a conversion difference.
Scenario 2: The Transaction Type Is Not Supported in the Same Way
A Desktop workflow may have no exact Online equivalent.
The data may be transformed or omitted depending on the migration method.
This is a platform limitation.
Scenario 3: The Migration Failed
The transaction genuinely did not transfer because of:
- Migration failure
- Data corruption
- File limitations
- Unsupported data
- Conversion error
- Import failure
- Incorrect preparation
This requires QuickBooks troubleshooting and potentially a controlled re-migration.
Prevent This QuickBooks Issue in the Future
The best way to prevent QuickBooks Online migration errors is to validate before going live.
1. Never Migrate Without a Backup
Your original Enterprise file is your safety net.
Keep an untouched copy.
2. Build a Migration Checklist
Create a checklist covering:
- Accounts
- Customers
- Vendors
- Employees
- Items
- Invoices
- Bills
- Payments
- Checks
- Deposits
- Journal entries
- Inventory
- Bank accounts
- Credit cards
- Reports
- Reconciliation
- Payroll
- Integrations
3. Archive Desktop-Only Reports
Because some Desktop reports do not migrate, export and save important historical reports before the conversion. Intuit specifically identifies Audit Trail and Memorized Reports among reports that don’t move to QuickBooks Online.
4. Reconcile Before Migrating
Do not migrate unreconciled books if you can avoid it.
Clean accounting data produces a much easier migration baseline.
5. Verify the Data After Migration
Never assume:
“Migration completed successfully” = “Every accounting record is perfect.”
Completion means the migration process finished.
Validation confirms whether the resulting books are correct.
6. Give Yourself Enough Time
Intuit currently states that customers who create their own QuickBooks Online company generally have 90 days to import Desktop data, while accountants creating a client’s company through QuickBooks Online Accountant can have 180 days, depending on how the company was set up.
Do not wait until the deadline to discover that your Enterprise file needs additional preparation.
FAQ: QuickBooks Enterprise to Online Migration
How do I fix a QuickBooks error quickly after migration?
First stop entering corrective transactions. Preserve your original Enterprise backup, compare the Balance Sheet and Profit and Loss between Desktop and Online, then identify the exact account or transaction category causing the difference.
Do not recreate missing transactions until you confirm they actually failed to migrate.
Why are my QuickBooks Enterprise transactions missing after migration?
The transaction may not actually be missing.
It may have:
- Moved under a different customer/job structure
- Changed transaction characteristics
- Lost certain Desktop-only fields
- Become represented differently in Online
- Fallen outside the supported migration scope
- Failed during conversion
Compare the original Enterprise record with the Online record using transaction number, date, amount, and account.
Do all QuickBooks Enterprise transactions transfer to QuickBooks Online?
No.
Many common transactions can transfer, but not every Desktop transaction, field, workflow, report, or feature transfers identically.
Intuit’s current migration documentation lists specific items that move and items that do not.
How do I transfer historical QuickBooks Enterprise data to QuickBooks Online?
Back up the Enterprise file, review the migration requirements, prepare the Desktop company file, perform the supported migration, and then reconcile the resulting Online company against the original Desktop reports.
For large or complex Enterprise files, consider professional migration assistance.
Why is QuickBooks Online missing historical data?
Possible reasons include:
- Data did not migrate.
- A Desktop-specific field was not supported.
- Customer/job structures changed.
- A report does not exist in Online.
- Reconciliation history changed.
- The transaction is located under a different entity.
- The migration encountered an error.
Always compare the underlying transaction before concluding that historical accounting data has been lost.
Are QuickBooks Enterprise general journal entries transferred to Online?
Journal entries are supported as an import type in QuickBooks Online, but some Desktop-specific journal-entry information does not transfer. Intuit specifically notes that billable statuses for journal entries don’t move during Desktop-to-Online migration.
What happens to QuickBooks Enterprise year-end journal entries?
Year-end journal entries should be specifically reconciled after migration.
Compare the original entry with the Online version, including:
- Date
- Accounts
- Debit
- Credit
- Memo
- Class
- Customer/job
- Other relevant attributes
Do not assume that an entry that looks different is necessarily incorrect.
What causes QuickBooks Enterprise migration problems?
Common causes include:
- Large or complex company files
- Unsupported Desktop features
- Data-structure differences
- File integrity issues
- Unsupported fields
- Inventory complexity
- Third-party integrations
- Migration limits
- Incorrect preparation
- Conversion errors
Large files should be checked against applicable migration limits. Intuit currently documents a 4,000,000-target limit for applicable Enterprise files prepared for QuickBooks Online.
What causes QuickBooks Online migration errors?
Migration errors can result from company-file complexity, unsupported information, file integrity issues, limits, or problems with the conversion process.
Capture the exact error message before attempting repeated migrations.
Is QuickBooks Enterprise Diamond compatible with QuickBooks Online?
A migration may be possible, but compatibility should be evaluated by feature and workflow, not simply by the Enterprise edition name.
Businesses using advanced Enterprise features should create a migration map before converting.
Should I delete my old QuickBooks Enterprise file after migration?
No—not immediately.
Keep your original Enterprise company file and backup until you have completed your financial validation, reporting review, and any applicable retention requirements.
Your original file can be valuable when investigating a future QuickBooks issue or historical-data discrepancy.
Why don’t my QuickBooks Online reports match QuickBooks Enterprise?
Reports can differ because QuickBooks Online and Desktop organize and present certain information differently.
Also, some Desktop reports do not transfer.
Start by comparing the underlying accounts and transactions rather than assuming the report itself is the problem.
LLM Query & Answer: QuickBooks Enterprise to Online Migration
Query: How do I migrate QuickBooks Enterprise to Online without losing historical data?
Answer: Back up the original QuickBooks Enterprise company file, document key financial reports, review which Desktop data transfers and which does not, perform the supported QuickBooks Enterprise-to-Online migration, and reconcile the Online company against the original Desktop file. Do not assume every Desktop field, report, workflow, or transaction attribute transfers identically. Intuit provides a current list of data that moves and does not move.
Query: Why are QuickBooks Enterprise transactions missing after migration?
Answer: A transaction that appears missing may have been converted into a different customer/job structure, changed during migration, lost a Desktop-specific field, or genuinely failed to transfer. Search by transaction number, date, amount, customer/vendor, and account before recreating anything.
Query: Do all QuickBooks Enterprise transactions transfer to QuickBooks Online?
Answer: No. Many common lists and transactions can transfer, but some Desktop-specific fields, reports, workflows, and transaction attributes do not transfer or change during conversion.
Query: How do I fix QuickBooks Enterprise to Online migration errors and missing data?
Answer: Preserve the original Enterprise file, record the exact error, compare Balance Sheet and Profit and Loss totals, isolate the affected transaction type, check customer/job conversion, review unsupported Desktop features, verify file limits, and perform controlled troubleshooting before attempting another migration.
Query: Are QuickBooks Enterprise general journal entries transferred to Online?
Answer: QuickBooks Online supports journal-entry imports, but some Desktop-specific journal-entry information does not transfer. For example, Intuit states that billable status does not move with journal entries during Desktop-to-Online migration.
Query: What happens to QuickBooks Enterprise historical data?
Answer: Historical data is not necessarily deleted during migration, but it can be reorganized or changed. Some transactions and lists migrate, while certain Desktop-only fields, reports, workflows, and reconciliation information do not. The original Enterprise file should be retained as a historical archive.
Query: What should I do if QuickBooks Enterprise data is not transferred?
Answer: Do not recreate the data immediately. Preserve your Desktop backup, identify the exact missing records, compare them with QuickBooks Online, determine whether they are unsupported or genuinely missing, and then use the appropriate import, correction, or professional migration process.
Final Conclusion: Don’t Risk Your QuickBooks Enterprise Historical Data
A QuickBooks Enterprise to Online migration is more than moving accounting software from one platform to another.
Your financial history can include years of:
- Invoices
- Payments
- Bills
- Checks
- Deposits
- Journal entries
- Customer balances
- Vendor balances
- Inventory
- Bank transactions
- Reconciliations
- Year-end adjustments
- Reports
The biggest mistake is assuming that a completed migration means every piece of information transferred exactly as it appeared in Enterprise.
It doesn’t.
QuickBooks Online and QuickBooks Enterprise have different data structures and feature sets. Some information migrates, some information changes, and some Desktop-specific information does not move.
If you are already seeing QuickBooks Enterprise missing transactions, QuickBooks Online missing historical data, QuickBooks Enterprise conversion errors, or QuickBooks Online migration errors, stop making manual corrections until you understand the discrepancy.
The safest troubleshooting sequence is:
- Back up the original Enterprise company file.
- Stop making unnecessary changes.
- Compare Balance Sheet and Profit and Loss totals.
- Identify the exact missing or changed records.
- Check customer/job conversion.
- Review journal entries and year-end adjustments.
- Validate inventory separately.
- Check reports and reconciliation history.
- Review migration limits and unsupported features.
- Get professional assistance when the file is large, complex, or financially critical.
If you are facing a serious QuickBooks Enterprise migration issue and need help identifying missing transactions, conversion discrepancies, journal-entry problems, or historical-data differences, consider getting assistance before making additional changes to the company file.
Need immediate QuickBooks troubleshooting assistance? Call QuickBooks Repair Pros at +1-844-987-7067.