I can speak about similar
integrations only, which my team has made. I'd imagine that getting Project Operations into Acumatica will involve.
1. Automated creation of the projects, making sure, that project naming follows rules of Acumatica. As alternative, Acumatica may have kind of truncation rules. Especially that is related to "Software development for Customer 1", or "Road construction between Mineapolis and Ohiyo".
2. Automated creation of Project tasks, and transition of hours/activities/materials from Project operations into Acumatica.
3. Making sure, that once something is deleted in one side, then it is automatically propogated to the other side ( if we want bi-directional sync ).
4. Dealing with corner cases, when project is completed, but needs to be reviewed, reopened, etc.
5. Sharing attachments between systems, as avaialble in one system, not necessary makes available in other one.
I can speak for Jira integration as an example. We had some attachments in Jira, which didn't travel through to Acumatica, and the alternative as well, attachments didn't migrate. Also Acumatica has notes, which was part of another additional development.
