GoDaddy Bookkeeping: Legacy Data and Migration Guide

GoDaddy Online Bookkeeping was a small-business income and expense tracking service associated with the earlier Outright product. It is retired and should not be evaluated as a current bookkeeping subscription. People searching for “GoDaddy bookkeeping” today usually need to understand an old report, find exported records, rebuild missing history, or migrate legacy data into a supported accounting system.

The old service agreement described features for entrepreneurs and self-employed users, including income and expense tracking and certain tax-oriented reports. A legacy feature description does not mean the service is currently available or that every former user’s data can still be retrieved. Use current official GoDaddy support for account-specific questions and never send credentials to an unofficial recovery service.

Start with the problem you actually have

• You possess CSV, spreadsheet, PDF, or tax-summary exports and need a usable archive.
• You need to move transaction history into current accounting software.
• You have only bank, card, marketplace, or tax records and must reconstruct the books.
• A tax form or prior return does not agree with the legacy reports.
• You need opening balances for a new system.
• You need evidence for an audit, notice, loan, sale, or financial review.

Do not begin by importing every file into a live accounting system. Preserve originals, identify the legal entity and period, and determine which source is authoritative for each type of data.

Preserve the legacy archive

Create a read-only archive of every available export, report, email, screenshot, tax summary, invoice, receipt, bank statement, credit-card statement, marketplace settlement, and prior return. Retain the original filename and modification date. Make at least one secure backup before opening or transforming files.

Record where each file came from, the export date, account or entity, period covered, columns, currency, and known limitations. Calculate a file hash when the archive will support a dispute or formal reconstruction. Do not overwrite an original file with a cleaned version.

Inventory the available data

Source	What it may contain	Important limitation
Transaction CSV	Date, description, amount, category, account	May omit attachments, split detail, or stable identifiers
Income and expense report	Totals by period and category	Summary cannot recreate every transaction
Bank and card statements	Independent cash and liability activity	Do not show every invoice, item, or business purpose
Marketplace settlement	Gross sales, refunds, fees, reserves, net deposit	Net bank deposits hide gross activity
Tax return and forms	Reported totals and tax classifications	May contain adjustments not present in bookkeeping exports

Build an account-and-period matrix. Mark each month for every bank, card, loan, marketplace, payment processor, and business entity as complete, partial, missing, or not applicable.

Determine the legal and accounting boundary

Confirm the taxpayer or legal entity, ownership, fiscal year, accounting method used for reporting, business accounts, personal accounts, and any changes in entity structure. Do not combine a sole proprietor, corporation, partnership, and household simply because the legacy service displayed them together.

Identify the last period supported by complete source records and the first period that must be reconstructed. If prior tax returns used a different classification or accounting method from the export, preserve both and obtain qualified advice before changing history.

Clean a transaction export safely

1. Copy the original into a working file and preserve the original unchanged.
2. Standardize dates, decimal signs, currencies, account names, and blank values.
3. Add source file, source row, entity, account, and import-batch identifiers.
4. Separate inflows, outflows, and balances consistently.
5. Flag duplicates using date, amount, account, description, and stable identifiers.
6. Identify transfers so both sides do not become income and expense.
7. Split net marketplace deposits into gross sales, refunds, fees, reserves, and other components.
8. Map old categories to the new chart without destroying the original category.
9. Route uncertain, personal, owner, loan, asset, and tax items to review.
10. Validate counts and dollars before importing a controlled test batch.

Never deduplicate on amount alone. Legitimate recurring purchases can share a value, and one transaction may appear under different posting dates across a bank and legacy export.

Build a category crosswalk

Create columns for legacy category, proposed new account, explanation, tax or reporting note, reviewer, and effective date. Preserve detail needed for management or tax work while avoiding a one-time chart with hundreds of nearly identical accounts.

Common high-risk mappings include transfers, owner contributions and withdrawals, loan proceeds and payments, sales tax, payroll, inventory, fixed assets, prepayments, customer deposits, reimbursable costs, refunds, and marketplace reserves. These should not be assigned by merchant name alone.

Reconstruct missing periods

When exports are incomplete, begin with independent statements. Enter or import bank and card activity, then add off-bank transactions such as invoices, unpaid bills, payroll liabilities, loan activity, cash purchases, marketplace reserves, and adjustments supported by other evidence.

The IRS explains that good records help identify income, expenses, and tax support. Its recordkeeping guidance identifies supporting documents generated by purchases, sales, payroll, and other transactions. Reconstruction should use the best available evidence and disclose estimates rather than presenting them as original facts.

Handle marketplace and payment deposits

Former GoDaddy Bookkeeping users often sold through ecommerce or marketplace channels. A net deposit can represent gross sales minus fees, refunds, chargebacks, shipping, advertising, taxes, reserves, or loan repayments. Reconcile the settlement report with the bank deposit and clearing account.

Check whether sales tax collected was included in gross receipts or held as a liability. Determine who was responsible for collection and remittance under the facts and current rules. Do not infer tax treatment solely from the deposit description.

Reconcile each source account

For every bank and card statement, compare the opening balance, statement activity, and ending balance with the reconstructed ledger. Complete periods chronologically because a wrong prior ending balance becomes the next opening difference.

Investigate missing items, duplicates, wrong dates, transfers, fees, interest, refunds, chargebacks, and transactions modified after import. Do not create an unexplained adjustment simply to reach zero.

Establish opening balances in the new system

The opening trial balance should come from a supported closing date. Cash and cards should agree with statements; loans with lender records; receivables and payables with item detail; payroll and taxes with filings; assets with schedules; and equity with the prior books and entity records.

If only income and expense exports exist, they may be insufficient to create a complete balance sheet. Document missing accounts and use qualified accounting and tax support to reconstruct material balances.

Choose a replacement system by requirements

Consider entity structure, cash or accrual reporting, bank connections, invoicing, bills, inventory, payroll, sales tax, ecommerce, projects, classes, currencies, users, permissions, audit history, exports, support, and total cost. A familiar interface should not outweigh complete accounting and data ownership.

Request a demonstration using representative transactions: gross marketplace settlement, transfer, refund, owner contribution, loan payment, asset purchase, payroll, sales tax, and month-end reconciliation. Confirm that reports can be traced back to transactions.

Test before full migration

Import one account and one complete period into a sandbox or controlled copy. Compare transaction count, inflows, outflows, ending balance, category totals, and exceptions with the source. Test split transactions, transfers, duplicates, refunds, and attachments.

Document the exact import settings and mapping. Delete or reverse test data only through a controlled process. Do not repeatedly import the same file into the production system.

Validate the completed migration

• Every expected account and period is present.
• Transaction counts and totals agree with controlled source files.
• Bank and card periods reconcile to statements.
• Marketplace and processor clearing accounts resolve.
• Receivable, payable, loan, payroll, tax, asset, and equity balances are supported.
• Prior tax-return totals are reconciled or differences are documented.
• Opening balances in the new system agree with the approved closing records.
• Users, permissions, integrations, backups, and exports are tested.

Control duplicate and transfer risk

Legacy systems, banks, marketplaces, and the new ledger can each contain a representation of the same economic event. Assign every source a role before importing it. For example, the marketplace settlement may be the source for gross sales, refunds, and fees, while the bank statement confirms the net cash deposit. Importing both as independent revenue creates duplication.

Use a stable transaction key when one exists. Otherwise combine source account, date, amount, currency, reference, and normalized description, then review possible matches. Exact duplicates can be strong candidates for controlled removal, while similar items need human judgment. Preserve the decision and original source row.

Transfers require two linked sides. A withdrawal from one bank and deposit to another are not an expense and income. Owner transfers, credit-card payments, loan funding, marketplace reserves, and payment-processor movements also need explicit mapping so the new ledger does not inflate revenue or expense.

Rebuild receivables and payables

A transaction export may show cash activity but omit unpaid customer invoices and vendor bills. Build a cutoff list from invoice systems, contracts, correspondence, year-end records, and subsequent receipts or payments. Record only valid open items and distinguish them from historical documents already settled.

Tie total customer and vendor detail to the new control accounts. Investigate credits, deposits, refunds, write-offs, and old balances. Do not create opening receivables or payables as one summary if the business needs customer, vendor, due-date, tax, or payment application detail.

Loans, assets, and equity

Bank activity alone may record a loan deposit as income and each payment as expense. Reconstruct the original principal, funding fees, payments, interest, and ending liability using lender records. Reconcile the balance at the migration date.

For significant equipment, property, or other assets, preserve purchase date, invoice, cost components, business use, financing, improvements, dispositions, and prior depreciation records. Separate owner contributions and withdrawals from revenue and expense according to the entity and facts. Obtain qualified advice when the old reports and filed returns disagree.

Parallel close after migration

For the first full month in the replacement system, compare bank and card reconciliations, income and expense totals, marketplace settlements, receivables, payables, loans, payroll, taxes, and the closing trial balance with the controlled migration records. Review reports with the owner and tax professional where appropriate.

Keep the legacy archive available and read-only during the validation period. Document every difference as timing, mapping, missing evidence, correction, or accepted policy change. Do not declare the migration complete while material unexplained clearing or suspense balances remain.

Tax-report comparison

Compare reconstructed annual income and expense totals with filed returns, Forms 1099, payroll filings, sales-tax records, and year-end financial statements. Differences can arise from accounting method, entity changes, tax-only adjustments, personal items, depreciation, inventory, and incomplete legacy data.

Do not revise a filed return solely because a newly imported report differs. Investigate the cause and obtain qualified tax advice about material corrections, amendments, notices, and retention.

Security during recovery

Legacy exports can contain account numbers, addresses, tax identifiers, customer information, and transaction details. Store them in a controlled encrypted location, limit access, use named accounts and multifactor authentication, and document secure deletion of temporary copies.

Beware of messages claiming they can reactivate the retired product or recover data in exchange for credentials. Verify current support contacts through the official GoDaddy domain. Do not provide passwords or one-time codes.

Records to retain

Keep the original exports, cleaned working files, crosswalk, import logs, exception list, statements, settlement reports, source documents, reconciliation packages, opening-trial-balance support, tax comparisons, reviewer approval, and final exports. The archive should let another qualified person reproduce material decisions.

Retention depends on the record and applicable requirements. Preserve basis, asset, loan, payroll, tax, ownership, and other long-lived records for as long as they remain relevant.

When professional help is useful

Seek help when records span multiple entities or years, prior returns disagree, payroll or sales tax is unresolved, inventory or assets are material, bank statements are missing, personal and business activity is heavily mixed, or an audit, notice, financing, or sale depends on the result.

Define whether the engagement covers data cleanup, bookkeeping reconstruction, tax advice, amended returns, migration, or ongoing monthly work. These are separate deliverables.

A controlled recovery sequence

Preserve first, inventory second, reconcile third, migrate fourth, and validate last. That order prevents an attractive new system from hiding gaps in the old records. Keep an exception log with amount, period, source, issue, owner, proposed resolution, reviewer, and status.

Approve the final archive, opening balances, unresolved-item list, and ownership of future work in writing. Record which system is now authoritative and the date on which ordinary monthly bookkeeping begins.

Continue with ecommerce bookkeeping, choosing a bookkeeping system, and general-ledger reconciliation.