Migrating from Tally to RetailPOS (India-specific playbook)

Most Indian retailers have an established division of labour between Tally and retail operations:

• Tally — accountant-driven; tracks the general ledger, GST returns, bank reconciliation, supplier-receivables, customer-payables, financial close. Updated weekly or monthly from till data + bills.
• Retail operations — shop-floor-driven; tracks daily sales, stock movement, cashier shifts, daily reconciliation. Today often runs on manual register + Excel + occasional basic POS.

The migration to RetailPOS doesn't replace Tally — it replaces the retail-operations layer. After migration:

• RetailPOS becomes the source of truth for daily retail (sales, stock, customers, suppliers from a purchase-receiving perspective)
• Tally remains the source of truth for accounting (general ledger, GST returns, financial close)
• Period-end export from RetailPOS to Tally bridges the two — weekly or monthly CSV export feeds Tally for the books

This division of labour fits the Indian retail accountant's working pattern. The accountant continues to use Tally; the shop owner uses RetailPOS; the period-end export keeps them aligned.

Tally's stock-item export is the cleanest source for catalog migration. From Tally Prime:

• Gateway of Tally → Display More Reports → Inventory Books → Stock Summary
• F12 Configure: show all detail columns (Cost Price, Selling Price, HSN/SAC, GST Rate, Stock Group, Unit), set period to current FY
• Alt+E to export → Format: Excel or CSV
• Export the file to a known location

The exported file typically has columns: Stock Item Name, Group, Sub Group, Unit, Opening Quantity, Closing Quantity, Cost Rate, Selling Rate (MRP), HSN/SAC Code, GST Rate. Some shops add Barcode + Brand + Category as custom fields.

Clean the file in Excel before importing to RetailPOS:

• Remove inactive items (zero closing stock + no recent sales)
• Standardise the unit column (PCS, KG, LTR, MTR, BOX, etc. — RetailPOS needs consistent values)
• Verify the HSN/SAC + GST Rate columns align with current GST schedules
• Add a barcode column if your shop scans items
• Add a category column if Tally Stock Group doesn't map cleanly
• For multi-state operations, ensure the per-state opening-stock allocation is clear (if Tally tracks per-godown, that maps to per-location in RetailPOS)

Aim for 85-90% accuracy at import time; correct remaining 10-15% after migration as you see them in daily operation.

From Tally: export customer + supplier masters with outstanding balances.

Customers: Gateway of Tally → Display More Reports → Statements of Accounts → Outstandings → Receivables; Alt+E export to Excel. The file has: Customer Name, GSTIN, State, Outstanding Balance, Phone, Email if captured.

Suppliers: Gateway of Tally → Display More Reports → Statements of Accounts → Outstandings → Payables; same export flow.

Clean both files: remove closed-out parties (zero balance + no recent activity), standardise phone format (10-digit + 91 prefix), verify GSTIN where captured (the 15-character format), ensure state names match Indian state codes for the IGST routing calculation.

Import customers + suppliers via the RetailPOS import flow with the outstanding-balance column populated. This creates the records with opening balances pre-set; future sales / purchases accrue on top.

If you're a covered retailer (above the ₹5 crore IRP threshold), e-invoicing was already running via your existing POS or GSP/ASP combination. The switchover:

• Pause e-invoicing submissions on the old POS the night before cutover.
• RetailPOS' onboarding pre-registers your GSTIN(s) with the GSTN API endpoint (1-3 business days lead time).
• On cutover day, the first B2B sale on RetailPOS generates the first IRN via the new integration; the receipt prints with IRN + QR.
• Verify the first 5-10 invoices appear correctly in the GSTN portal; if so, the cutover is clean.

Common mistake: forgetting to terminate the old GSP relationship after cutover. The old GSP may continue to bill you for API access until explicitly cancelled. Cancel within the first week post-cutover.

For below-threshold retailers (most single-shop kirana / mobile / salon operations), no e-invoicing switchover needed — operate without IRP integration until you cross the threshold, then activate it without re-onboarding.

After cutover, RetailPOS is the retail source of truth; Tally remains the accounting source of truth. The period-end export bridges them.

Frequency: most accountants prefer weekly export for active shops, monthly for slower operations. The RetailPOS export produces:

• Sales register CSV — all sale transactions with date, customer (GSTIN if captured), HSN+GST split, total. Maps directly to Tally Sales Vouchers.
• Purchase register CSV — all purchase-receipt transactions with supplier (GSTIN), HSN+GST split, total. Maps to Tally Purchase Vouchers.
• Inventory adjustment CSV — stock movements that aren't sales or purchases (transfers, write-offs, opening adjustments). Maps to Tally Inventory Vouchers.
• Cash + UPI + card settlement summary — bank-reconciliation-ready format. Maps to Tally Bank Statements / Receipt Vouchers.

Your accountant imports these into Tally via Tally's standard data-import flows; the GSTR-1 and GSTR-3B preparation flows in Tally use the imported data. The format is designed to align cleanly with Tally Prime's import schema.

For covered retailers running RetailPOS e-invoicing, the e-invoicing data also auto-populates GSTN's GSTR-1 auto-draft independently of Tally; the Tally export is then a parallel reconciliation check rather than the primary GSTN data source.