EPESI Web Hosting with Free Domain

EPESI Overview and Features

Ways to Use EPESI

Installing EPESI

RSH Web Services offers EPESI installation through Softaculous in cPanel. Use the installer first to create the application files and any required database or administrator account. For manual installation, obtain the trusted current package, follow its official instructions, protect configuration and storage paths, and apply only documented permissions. RSH Web Services can help with installation.

Migrating or Upgrading EPESI

Begin with cPanel backups of the application, configuration, database when used, and all managed files. For a Softaculous-managed installation, use only the backup, clone, restore, or upgrade controls displayed for EPESI before manual steps. Follow the documented version path and test users, roles, records, imports, reports, documents, integrations, and scheduled jobs on a private copy. Softaculous upgrades EPESI only; it does not convert another CRM, accounting, or collaboration platform into EPESI.

EPESI Security

Restrict access to trusted users, use unique credentials, apply least-privilege application and filesystem roles, protect customer and financial records, and secure configuration and uploaded-document paths. Review logs, remove unused accounts, and install supported security updates after testing. Hosting protections add useful layers but cannot repair unsupported application code or prevent damage by an overprivileged account.

Backups and Recovery

Back up the application, configuration, database when used, user accounts, roles, customer or financial records, transactions where used, documents, reports, and configuration needed for recovery. Keep multiple dated restore points and at least one copy outside the hosting account. Restore a private copy periodically and confirm that users, roles, records, transactions, documents, reports, email, and scheduled jobs work together.

All EPESI Plans Include

EPESI Resources

Existing software and hosting resources: Website Hosting.

Frequently Asked Questions

How should user roles be configured in EPESI?

Give each person only the permissions required for their work. Separate system administrators, managers, finance users, sales or service staff, and read-only users as the application allows. Test every role with a non-administrator account, document who can export, delete, invoice, change settings, or view sensitive records, and review access whenever responsibilities change.

What customer data should be stored in EPESI?

Store only information needed for a defined business or organizational purpose. Establish rules for contact details, communications, financial records, notes, uploaded documents, and custom fields. Avoid unrestricted free-form notes containing unnecessary sensitive data. Document the lawful basis, retention period, correction process, export procedure, and deletion responsibilities that apply to each record category.

How should duplicate contacts be handled in EPESI?

Define a matching process before importing data, using reliable identifiers such as organization, email, account number, or another approved field. Review suspected matches manually when records contain transactions or activity history. Merge only with a tested procedure, preserve ownership and relationships, and keep a backup so an incorrect merge does not permanently damage customer or organizational records.

What should be tested before updating EPESI?

Create matched backups and reproduce the installation in a private staging location. Follow the official upgrade path for the exact source and target versions. Test logins, roles, contacts, searches, imports, exports, email, reports, documents, scheduled jobs, enabled modules, and integrations. Confirm that the rollback procedure works before applying the update to production.

Can EPESI replace an independent backup system?

No. Application features organize records but do not protect against a compromised administrator, failed upgrade, damaged database, deleted files, or account-level outage. Back up the application, configuration, database, uploaded documents, custom modules, and scheduled-task settings as one recovery set. Keep dated copies outside the live account and periodically test a private restoration.

How should email integration in EPESI be secured?

Use a dedicated mailbox or approved service account, modern authentication where supported, and the minimum mailbox permissions necessary. Protect tokens and credentials, restrict who can send or read messages, and review logs for failures or unusual activity. Test threading, attachments, retention, opt-out handling, and shared-mailbox behavior before connecting a production customer mailbox.

How do I migrate records into EPESI?

Clean and map source fields before import, then test a small representative batch. Preserve stable identifiers for organizations, contacts, transactions, activities, and ownership where supported. Check character encoding, dates, currencies, required fields, attachments, and duplicate rules. Compare record counts and sampled relationships after import, and retain the original export until users approve the result.

What reports should be checked after moving EPESI?

Compare totals and record counts for customers, contacts, open activities, financial documents, projects, tickets, or other enabled modules. Run the same date ranges and filters on both systems, then inspect samples with attachments and linked records. Differences should be explained before launch, especially where reports support billing, accounting, compliance, or operational decisions.

How can EPESI be recovered after a failed change?

Stop new activity and preserve the current application files, database, configuration, uploads, and logs. Restore a matched backup set to a private location and test logins, permissions, records, searches, reports, documents, email, and scheduled jobs. Avoid combining files and databases from different dates. Record the failure cause before attempting the change again.

Share This EPESI Hosting Page

 Tweet  Share  Pin  Email

Hosting Guarantee

RSH Web Services provides a 45-day money-back guarantee for EPESI hosting.