01
Example deployment
Authorised users → approved remote access method → Windows or supported application server → business data and agreed backup jobs. Software entitlement and vendor compatibility determine the final design.
SOLUTIONS THAT START WITH YOUR BUSINESS
Tally & ERP Infrastructure
Review server resources, application compatibility, user access and licence responsibilities for business accounting or ERP workloads.
Workload assessmentConfiguration planningMigration & handover
PLAN THE COMPLETE ENVIRONMENT
Application
Business data
Infrastructure
Start with the business workflow
Accounting and ERP environments carry business records that need careful access and recovery planning. Identify the exact application and vendor-supported versions, current data size, concurrent users and connected offices. Include printers, exports and integrations. Obtain software compatibility and licence requirements from the vendor before choosing the operating system or remote access model.
Practical challenges to plan for
A server configuration does not include a Tally, ERP, Windows or Remote Desktop licence by default. Concurrent user access can involve additional software rights. Document how staff sign in, who approves access and who supports the business application. Check recovery with the person responsible for accounting or operations rather than judging it solely by whether a server starts.
Example configuration
A discussion starting point. Resource sizes, availability, licences and performance must be validated for your workload.
02
Configuration inputs
Application edition, vendor requirements, authorised users, Windows / RDS licensing and backup validation.
03
Operating model
Your team owns the application and business validation. Ask for scoped server management, monitoring or backup administration if you need those tasks assigned to CloudLelo.
Confirm the important decisions
A quotation connects the workload to the supplied environment.
| Decision | What the team should agree |
|---|---|
| Resources | Measured CPU, memory, storage and growth assumptions. |
| Software | Supported versions and separately required licences. |
| Access | Authorised users, administrators and approval contacts. |
| Recovery | Protected data, retention and restore validation. |
| Management | Named recurring tasks, maintenance and application exclusions. |
Choose an operating model
Your application owner and server administrator need a shared view of responsibilities. Identify who approves changes, updates application software, manages accounts and handles incidents. CloudLelo can quote the specific operating-system or infrastructure tasks required. Application development, software vendor support, licences and provider charges are separately reviewed. Use the management scope as an operational reference, and update it when new integrations or environments are introduced.
Move with acceptance criteria
A migration depends on the actual application and the source environment.
01
Inventory
Collect versions, data size, dependencies and current resource use. Confirm who owns DNS and licences.
02
Prepare
Check compatibility, choose the destination and agree backup and transfer methods.
03
Validate
Test the important business workflows before traffic changes. Record the application owner’s acceptance.
04
Cut over
Agree the change window, data consistency and rollback decision. Keep the source available for the approved transition period.
Questions before choosing a configuration
Describe your workload so the team can scope the proposal.
Which server size should we select?
Start with application edition, vendor requirements, authorised users, windows / rds licensing and backup validation. Measure the current workload and review growth rather than relying on visitor or user counts alone.
Is application support included?
Application development and software vendor support are separately scoped. A management agreement lists the server and application tasks it covers.
Are licences part of the resource price?
Software rights depend on the application and access model. The quotation itemises applicable licences and any customer-supplied entitlement.
Can an existing environment move?
Compatibility, transfer method, data changes and acceptance tests are reviewed before a migration is agreed.
Are backups included?
The quote identifies backup jobs, retention and restore tasks when selected. They are not automatically included with every environment.
How do we request a proposal?
Share the application, current resources, authorised users and migration needs. Avoid including passwords or private business records.
LET’S TALK ABOUT THE NEXT STEP
Tell us what your business needs to run.
From a new server to an existing application migration, start with your workload and leave with a clearly defined scope.