Where is Tally data stored? In TallyPrime, company data is stored in the configured Company Data Path. Tally’s own documentation says the default company data location is the path configured for company data, and the About screen can show the “Location of Company Data.” You can change that path depending on your single-user, LAN or hosted setup.
This matters when moving Tally from an office PC to a cloud Windows server or VPS. The hosting provider supplies the server environment; the business still needs a clear data path, access controls, backup location and restore procedure.
How to find the Tally company data location
TallyPrime’s About page includes data information such as:
- Location of Company Data;
- Location of Company Backup;
- companies configured to load on startup;
- Tally Gateway Server information where applicable.
Tally also documents the Company Data Path configuration under its data settings. If you are migrating, record the exact path before copying anything.
Local Tally data vs cloud-hosted Tally data
| Model | Where data lives | Main operational issue |
|---|---|---|
| Single office PC | Local company data path on that computer | Hardware and office become single points of failure |
| LAN/server | Shared server/data location | LAN/server availability and backup discipline |
| Hosted Windows VPS | Company data path inside hosted Windows environment | Remote access, licences, backups and security |
| TallyDrive backup | Cloud backup service for supported TallyPrime releases | Backup is not the same as the live working data path |
Should you copy the Tally data folder directly?
For ordinary backup and transfer, use Tally’s supported backup/restore workflow rather than treating the live company folder like a generic document folder. Tally’s own guidance recommends regular backups and describes backup/restore as the safer method for recovery and moving data.
Where should Tally backups be stored?
A backup should not exist only beside the live data on the same disk. Tally’s documentation recommends regular backup and supports local-drive and TallyDrive backup options in current releases.
For a hosted server, use at least two layers:
- application-aware Tally backup;
- independent off-server/server-level backup according to the agreed retention.
Test restoration. A backup file that has never been restored is not proven recovery.
Tally on cloud: what the VPS changes
Moving Tally to a Windows VPS changes the infrastructure location and access model. Staff connect remotely to the hosted Windows environment instead of depending on one office machine.
Benefits can include:
- access from authorised branch/home devices;
- centralised server resources;
- cleaner backup scheduling;
- less dependency on one office desktop;
- easier resource upgrades when user count grows.
It does not remove the need for Tally licensing, Windows/RDS licensing where applicable, secure credentials and application support.
How much VPS capacity does Tally need?
Size from simultaneous users and workload, not from total employee count. Monitor Windows CPU, available RAM, disk latency and remote-session experience during busy periods. A file/data workload may appear light until several users post transactions, run reports and export files at the same time.
Tally RDP security checklist
- Give users separate credentials.
- Do not share one administrator login.
- Restrict RDP exposure where possible.
- Patch Windows and security software.
- Define who can access backup files.
- Keep application and infrastructure responsibilities documented.
Cloud vs local Tally: the actual decision
Local hosting can be reasonable for a single office with reliable hardware, power, IT support and backup discipline. Cloud hosting becomes attractive when staff need remote access, branches share data, office hardware is a risk, or recovery needs to be more structured.
Bottom line
Tally data is stored in the configured Company Data Path. Before moving it to cloud hosting, identify that path, take a supported backup, define the new hosted data path, secure remote access and prove the restore process.
Next step: review StreamData’s Windows VPS options and provide simultaneous-user count, current data size and backup requirements for a Tally hosting recommendation.
Frequently asked questions about Tally data storage
Is the Tally backup folder the same as the live data folder?
No. TallyPrime lets you configure company data and backup paths separately. Keep backups separate from the live working data so a disk or folder-level incident does not remove both copies.
Can I put Tally data directly in a generic synced folder?
Do not improvise the live data architecture. Use Tally-supported data paths, server modes and backup/restore workflows appropriate to your release. Generic file synchronisation can create consistency risks if multiple users are writing data.
What should I record before moving to cloud?
Record the current Company Data Path, company list, Tally release, user count, licensing model, backup path, data size and any integrations. Take a verified backup before changing the environment.
Does a cloud VPS automatically back up Tally?
No. Hosting and backup retention are separate unless the service scope explicitly includes them. Define both Tally-aware backup and infrastructure-level recovery.
Related: StreamData city/node selection guide.