
- System availability: Look for a vendor that can commit to 99% availability or higher.
- Disaster recovery: If there’s a data center disaster, make sure that you’ll be back up in 24 hours, and that you’ll lose no more than 2 hours of data.
- Data integrity and ownership: If you decide to leave your cloud vendor in the future, you should be able to get your data out of the vendor’s system—period.
- Support response: As a general rule, your vendor should be transparent about what constitutes a high-priority, medium priority, and lower priority issue—and should be able to respond to high- priority requests within one to two hours.
- Escalation procedures: If you have a support case that you feel needs to be escalated, you be provided with a clear escalation path and the contact information of at least three people to contact.
- Maintenance communication: Your vendor should let you know when regular recurring maintenance activities take place, and should post a special notification if any maintenance activity is expected to take longer than normal.
- Product communication: Your vendor should commit to providing regular updates on new product features and product release notes.
- Why most financial software systems hinder your ability to get good financial information.
- The six key questions you need to ask before considering a move to a cloud-based financial solution.
- Why the process for evaluating software is different for cloud solutions—and the seven things to make sure you’ve got in writing.
- Case Study: Intacct Streamlined Reporting for Potential Church
- The Importance of Enterprise-Ready Software
- Five Things to Look for in Cloud Accounting Providers