Skip to main content
Integration Management

Scalable Data Synchronization for Enterprize Organizations.

Say goodbye to expensive custom integrations! The Projectum Integration Hub is a flexible, user-friendly data synchronization platform that connects your business-critical systems – on every scale. 

Integration Management-hero.jpg

See the health of your integrations

Large enterprises have many integrations and when they go wrong it can be difficult to spot. With our integration management, you can see your integrations, monitor their status, and support your tech stack as it evolves. 

/

The ability to extend Projectum xPM with complementary solutions, like PowerApps, SharePoint, SAP and Power BI integrations, has delivered a scalable platform that adapts to Vattenfall Services way of working and allow us to use AI on structured data.

Anna Nyberg
Business Developer, Vattenfall

Certified connectors for the enterprise stack 

Microsoft Ecosystem_1.jpg

Microsoft Ecosystem

Support your Microsoft ecosystem, from project management, to workflows, reporting and security. 

Delivery & ITSM_1.jpg

Delivery & ITSM

Keep your portfolios in sync with Jira, Azure DevOps, ServiceNow, and Microsoft Fabric, so delivery status flows up without anyone re-typing it. 

Finance, CRM, and People_1.jpg

Finance, CRM, and People

Pull cost actuals, budgets, people, and rates from SAP, Dynamics 365 F&O, Salesforce, Workday, and Snowflake. 

FAQs

All about Integration Management

  • The Integration Hub is a dedicated integration application that keeps Projectum xPM in sync with the tools your teams already work in, such as Azure DevOps, Jira and your finance systems. It is deployed into your own Azure subscription, so your data flows directly between your systems and never passes through a third-party cloud. You configure integrations in a web interface: connect a system, map the fields, choose how records are matched, and decide whether the sync runs on a schedule or reacts to changes as they happen. 

  • Out of the box, the Hub connects Microsoft Dataverse (where Projectum xPM lives), Azure DevOps, Atlassian Jira, Microsoft Planner, Dynamics 365 Business Central, SAP (HANA and SuccessFactors), SQL Server and Azure SQL, SharePoint, and flat files such as CSV and Excel. A generic REST API connector covers systems beyond that list, so most in-house tools can join without custom development. And because everything lands in Dataverse or SQL, Power BI can report on it immediately. The list keeps growing, so get in touch if your system isn't named here.

  • The Hub runs entirely inside your own Microsoft tenant and Azure subscription, in the Azure region you choose, which keeps you in control of data residency. Data moves directly between your systems; Projectum never processes or stores it. Sign-in goes through your Microsoft Entra ID with role-based access, connection credentials are stored in Azure Key Vault, and every sync run is logged down to the individual record, so you always have an audit trail.

  • No. The Integration Hub doesn't use Power Platform connectors at all. It talks to each system directly through service-to-service authentication, so there is no per-user integration licensing to buy. The Hub runs on a small set of standard Azure resources in your own subscription, and that consumption is the only running cost.

  • The timeline depends on your current setup, field mappings and internal governance. With the standard connectors it's a matter of days, and the deployment itself is a script we run together in your Azure subscription. The difficult variable is permissions: customers who grant the needed Azure and Entra ID permissions up front are typically up and running the same day. The best part is that the first integration does the heavy lifting; every one after that reuses the same setup and takes hours, not weeks.

  • No. Integrations are configured, not coded: you connect a system, pick the entities, map fields in the UI and set a schedule. Even most in-house tools can be reached through the built-in REST API connector. Developer effort only comes into play for systems with no API at all. 

  • One-way is fine for read-only reporting. Two-way is needed the moment portfolio managers change dates or budgets and delivery teams must see it in their own tool. The Hub supports both per entity, you decide the direction for each mapping, and key-based matching makes sure a change updates the existing record instead of creating a copy.

  • Yes. Every mapping has a preview mode that runs the integration as a dry run and shows you, record by record, what would be created, updated or skipped, before anything is written. You review the result, adjust the mapping if needed, and only then let it run for real. 

  • Your choice, per integration. Run syncs on a schedule (with incremental sync so only changed records move), trigger them manually, or make them event-driven so a change in Jira, Azure DevOps or Dataverse flows across within seconds of being saved.

  • Failures are never silent. Every run and every record is visible in the built-in monitoring, failed records carry a plain-language explanation of what to fix, temporary outages are retried automatically, and the Hub can email your team when something needs attention.