We are thinking about splitting up our CommitCRM database into two separate ones (onsite/remote support) and internal (walk-in repair). The workflow flexibility just isn't there (one of by biggest gripes about Commit) to handle the two different types of tickets in the same instance. Has anyone else done this, and could it also be done with the SQL version (thinking about moving to that as well)? Lastly, has anyone tried syncing two different CommitCRM databases to the same QuickBooks file?
Announcement
Collapse
No announcement yet.
Multiple Databases
Collapse
X
-
northwestmsp
- 157
Multiple Databases
-
northwestmsp
- 157
Re: Multiple Databases
No answers or ideas from anyone?
-
nattivillin
- 1146
Re: Multiple Databases
You may be the first to attempt this. Ive found CommitCRM to be pretty good at separating clients and types of jobs, so I've never encountered the need for 2 db's.
I would love to use it for our walk in clients at all our stores, but installing qb on every pos machine, and then having to dump those sales into a master QB db just isnt worth it to me.
Comment
Comment