Can any old software file be uploaded directly?
No universal converter is promised. Confirm supported CSV templates and migration scope with the authorized administrator before preparing files.
Fertilizer Shop Data Migration Checklist
Short answer
Data migration starts with a cutover date and a reconciled set of records. Decide what will become opening stock and balances and what history must remain accessible. Confirm the available import workflow before preparing files; Kroply’s administrative CSV import is not a universal file converter or a standard counter-screen feature.
Define the cutover and keep the originals
Choose the date and time when new transactions will move to the new system. Retain an unchanged copy of the old export and supporting reports. Record which transactions occurred after that copy. Avoid letting two systems independently become the final record for the same sale or receipt during the switch.
Agree supported files with the administrator
The administrative import tooling uses CSV templates for supported record types, including customers, suppliers, products and sales. Confirm the intended account, shop, record type and template with the authorized administrator. Use the current template rather than guessing column names. Do not assume an Excel workbook, another vendor’s database or every historical attachment can be imported directly.
Clean identity and units before loading
Check duplicate customer and supplier names against contact and source details. Normalize product pack sizes and units without merging genuinely different variants. Keep a written mapping from old identifiers to the intended records. Resolve missing required columns before the pilot and inspect any optional fields that would receive default values.
Worked opening-record check
Illustrative example: physical opening stock is 30 bags of one product and customer A owes ₹4,000 at cutover. If historical sales already establish that ₹4,000 receivable, adding another ₹4,000 opening balance would double it. Agree whether the imported history or an opening entry is the source for that amount. Use the same reasoning for stock so opening quantity and historical movements do not both add the same goods.
Pilot before the full import
Ask the authorized operator to load a small representative sample through the supported workflow. Check record counts, customer balances, supplier balances, product units and stock quantities against your control sheet. Include a duplicate-name case and a product with a different pack size. Investigate rejected rows rather than assuming an accepted file means every source record is correct.
Reconcile and keep an exception list
After the agreed import, compare totals and individual sample records before starting normal billing. Record missing or disputed rows separately with their source references. Confirm how corrections will be handled before adding new activity; import reversal has eligibility rules and is not a promise of unrestricted undo. Retain the old records for reference and agree access with the people responsible for the business records.
Questions and answers
Should history and opening balances both include the same dues?
No. Agree one source for the cutover amount and reconcile it so the same outstanding is not counted twice.
Related resources
How Kroply handles this
Kroply provides connected shop billing, inventory, supplier records, reviewable OCR, customer credit, expenses and reports. Core workflows require internet, and staff and shop allowances depend on the current plan.
Things to consider
Test your own purchase, sale, receipt and return. Compare devices, printing, languages, migration scope, current pricing and support channels using the same requirements.