Make sure that you have any business processes you are planning on implementing in FileBound mapped out completely and in very much detail. This will help you ensure that you are re-creating the client's business process as it currently exists.
Additionally be prepared for scope creep and be prepared to push back on it. As clients start to see and learn about the different features within FileBound they become a "kid in a candy store" and want every feature they see implemented in their new process. This is all well and fine and understandable, but you must be prepared to tell the client "not yet", and make sure you get the system implemented first. Trying to include scope creep in an initial implementation is a recipe for disaster, and will very easily cause system implementation to fail. It is best to first recreate the business process in FileBound as it is currently used so that users completely understand what they are doing in the system on a day to day basis. Once the system is implemented you can move onto "Phase 2 and Beyond", which is adding features and functionality that the client would like to improve their current process with. Review collected by and hosted on G2.com.