Dynamics 365 Project Operations and Business Central Integration: Automate Data Sync Without Manual Work

Please find this CloudFronts Product at – CloudFronts PO-BC Integration Module | Microsoft Marketplace

Watch the webinar – CloudFronts PO-BC Integration Webinar | YouTube

Summary

Table of Contents

1. 1Introduction
2. 2Business Challenge
3. 3Why an Integration Hub?
4. 4Implementation Procedure
5. 5End-to-End Working
6. 6Why This Approach Works
7. 7Real-World Use Cases
8. 8Frequently Asked Questions
9. 9Conclusion

Introduction: Why Connect Dynamics 365 Project Operations with Business Central

Many project-based businesses use two systems. Project Operations (PO) is where the sales and project teams keep customers, projects and time. Business Central (BC) is where the finance team keeps invoices, payments and money records.

Both systems need the same details. A customer made in PO must also exist in BC. A project made in PO must also be there when it is time to send an invoice. Without a link, someone has to copy all of this by hand.

Here is the full picture of how work moves from a lead to a payment. The top row is PO and the bottom row is BC. The arrows show where the two systems share data.

Business Challenge: Manual Data Entry Between PO and BC

Think about a normal project business. The sales team makes a customer in PO. The project team makes a project and adds tasks. The finance team then needs the same customer and project in BC to send invoices.

These details need to be shared between the two systems:

1. Customers and contacts
2. Projects and tasks
3. Planned work and costs
4. Approved time and expenses
5. Vendor invoices and purchase orders
6. Paid status of invoices

When people copy these by hand, many problems come up:

1. Extra effort: The same details are typed in two systems.
2. Mistakes: A wrong phone number or address is easy to type.
3. Details that do not match: The two systems slowly stop agreeing with each other.
4. Late invoices: If data reaches finance late, money comes in late.
5. Hard to grow: More customers and projects mean more copying and checking.

Why Use an Integration Hub for PO and BC Integration?

The Integration Hub is one place where you create and manage every link between PO and BC. You fill a form, choose what to send, and set simple rules. You do not need to write a lot of code.

With the Integration Hub, you can:

1. Set up each link once
2. Choose what data moves, from where, and to where
3. Write simple rules for which detail goes where
4. Test the result before it goes live
5. See all links in one list, with their status and last runs
6. Add new links as your business grows

Implementation Procedure: How to Integrate Project Operations with Business Central

Step 1 – Choose the Project

On the first screen you pick a project. A project here is a group of links. We use the project named PO-BC, which is for Project Operations and Business Central.

Step 2 – See the List of Integrations

Inside PO-BC you can see all the links. Each row shows its order number, its status, and its last few runs. You can run, edit or deploy each one from here. To add a new one, click New Integration.

Step 3 – Fill the New Integration Form

A form opens on the right side. Here you tell the platform:

1. Integration Name: A name for this link. For example, Accounts.
2. Integration Type: Master means basic details that rarely change, like customers. Transactional means things that happen often, like invoices.
3. Source System and Source Entity: Where the data starts, and what kind of record it is. Here the system is PO, and the record type is accounts.
4. Target System and Target Entity: Where the data goes, and what kind of record it becomes. Here the system is BC, and the record type is customer.
5. Sequence No.: The order in which links run. Customers must exist first, so this is 1.

Scroll down and add a short description. This helps everyone understand later what the link does. Then click Create Integration.

Step 4 – Open the Flow

After you create the link, you can open its flow. It is a simple picture with boxes from left to right:

1. Source: the PO data (accounts)
2. Data Mapper: the rules that change the data into the shape BC needs
3. Target: the BC data (customer)
4. Return to Source: an optional step to send data back to PO

Step 5 – Write the Mapping Rules

PO and BC use different names for the same thing. For example, PO calls the company name name, and BC calls it Name. PO has telephone1, and BC has Phone_No. A list that says which detail goes where is called a mapping.

A Liquid template is a small piece of text where you write these rules. Click Edit Liquid, write the rules, and click Save & Apply.

Step 6 – Test Before You Go Live

Click Run to see the result. The console at the bottom shows exactly what will be sent to BC. You can check the values, like the name and customer number, before anything goes live.

End-to-End Working: How Project Operations Syncs Data to Business Central

Once a link is set up, it works on its own. Here is the full process:

1. A person creates or changes a record in PO, like an account.
2. PO keeps its data in a place called Dataverse. Dataverse notices the change.
3. Dataverse wakes up a Logic App. A Logic App is an automatic helper that does the copying work for us.
4. The Logic App reads the new data and uses the mapping rules to put each detail in the right place.
5. The Logic App sends the data to Business Central.
6. BC creates or updates the record, like a customer card with its own customer number.

Example: An Account in PO Becomes a Customer in BC

Let us see how this looks for a real record. We use a test account called Boston Consulting Group.

In Project Operations. Accounts are created in PO under the Sales area, in the Customers section.

An account can be a Customer or a Vendor. Customer accounts show under Customers. Vendor accounts show in the Project area under Vendors. Here is the Boston Consulting Group account with its phone, website and address.

In Business Central. Now we open BC and search for Customers. The same company is in the list, with its own customer number, C00270.

When we open the customer card, we see the same name, phone number, address and website that we entered in PO. Nobody typed them again.

Why This Approach Works for Dynamics 365 Integration

• No Double Typing Data is entered once in PO. It does not need to be typed again in BC.
• Fewer Mistakes Data is copied by rules, not by hand, so there are fewer typing errors.
• Same Details Everywhere PO and BC show the same details, so everyone trusts the numbers.
• Faster Billing Approved work reaches BC quickly, so invoices can go out sooner.
• Easy to Test You can see the result with the Run button before anything goes live.
• Easy to Grow To add a new link, create a new integration. The work does not multiply.

Real-World Use Cases for Project Operations and Business Central Sync

Customers are only the start. Here is the detailed flow. PO is on top, BC is below, and the arrows show the data being shared. Each arrow can be one integration in the Integration Hub.

Frequently Asked Questions

Conclusion

A Dynamics 365 Project Operations and Business Central integration saves time and removes manual work. When PO and BC are not connected, teams spend their time copying data, fixing mistakes and waiting for invoices. The Integration Hub turns this into a simple process: choose the source and the target, write the mapping rules once, and test them. After that, every change in PO reaches BC by itself.

We have built and tested this in our own sandbox, and we plan to keep adding more integrations.

About the Author

Aryan Shukla

CRM & Data Engineer · CloudFronts

I’m Aryan Shukla, a CRM & Data Engineer at CloudFronts. I have experience in CRM and in building practical solutions with data, cloud, and AI.

Specialization: Data Engineering, Dynamics 365 CRM, Power BI, Azure, Databricks.

LinkedIn