Common Questions
- Do we have to migrate to the budget changes feature?
- How long can we continue to use budget modifications?
- Do we need to update our API integration before migrating to budget changes?
- Which API endpoints are being deprecated?
- Can we sync budget changes with our integrated ERP system after the migration?
- Can we sync budget modifications with our integrated ERP system after the migration?
- Are there any other requirements?
- How will a migration to budget changes affect reporting?
Do we have to migrate to the budget changes feature?
Yes. Procore's new Budget Changes feature was designed in response to user feedback and is a substantial upgrade to budget modifications. Procore is working with all customers to migrate their existing budget modifications data to the new budget changes format. Procore is providing customers with more than one (1) year to complete this migration process. Migration must be complete by a date yet to be determined.
How long can we continue to use budget modifications?
The new Budget Changes feature is designed to replace the existing budget modifications feature. Starting in October 2022, Procore will be working with Procore customers to migrate their existing budget modifications data to the new format required for the Budget Changes feature. Migration must be complete by a date yet to be determined. Once you complete this migration, you will no longer have access to the budget modifications feature. If you have any questions before your company starts the migration, contact your Procore point of contact.
To learn about the migration process, see Migrating to Budget Changes from Budget Modifications.
Do we need to update our API integration before migrating to budget changes?
Yes. Your Procore API endpoints will need to be updated as follows:
- If you have a Procore-built ERP Integration (see ERP integrations), your API endpoints have already been updated to support the migration to the budget changes feature. If you have any questions about the migration, contact your Procore point of contact.
- If you have a custom API integration built by Procore Technical Services, please do NOT perform the migration to budget changes on your own. To avoid unexpected results, it is important that you plan and schedule your migration to the budget changes feature. To schedule your migration, please send an email to apisupport@procore.com.
- If you have developed an API integration on your own or with a third-party technology partner, you must update your integration’s API endpoints before you can start using the budget changes feature. See the Which API endpoints are being deprecated? below for the affected API endpoints.
Important
How much time do we have to update our API integrations to the new API? To support our customers in their long-range planning processes and to provide users with ample notice of this update requirement, Procore expects to sunset these legacy endpoints at a later date that is yet to be determined.
Which API endpoints are being deprecated?
Procore is notifying our customers now that the following endpoints are listed as deprecated in the Reference documentation on
developers.procore.com. Procore expects to sunset these legacy endpoints in November of 2024:
- List Budget Modifications - GET /rest/v1.0/projects/{project_id}/budget_modifications
- Show Budget Modification - GET /rest/v1.0/projects/{project_id}/budget_modifications/{id}
- Create Budget Modification - POST /rest/v1.0/projects/{project_id}/budget_modifications
- Update Budget Modification - PATCH /rest/v1.0/projects/{project_id}/budget_modifications/{id}
- Delete Budget Modification - DELETE /rest/v1.0/projects/{project_id}/budget_modifications/{id}
Can we sync budget changes with our integrated ERP system after the migration?
Yes. If you have a Procore-built integration and you have completed the migration process, you can sync budget changes with the ERP Integrations tool.
Can we sync budget modifications with our integrated ERP system after the migration?
No. If you have completed the migration process, you will no longer be able to sync your budget modifications data with the ERP Integrations tool.
Are there any other requirements?
Yes. The migration process also requires the users at your Company to use the modernized Change Events experience. To learn about the experience, see Project Financials: Modernized Change Events Experience.
How will a migration to budget changes affect reporting?
If you have included budget modifications in your existing reports, you will need to be aware of the following:
-
Budget Snapshots
-
Budget modifications will continue to be available and reportable.
-
Budget changes will show once new snapshot(s) are created.
-
- Enhanced Reporting for Financials. See Reports: Enhanced Reporting for Financials.
-
Budget modifications are removed.
-
Budget changes are included if users add a 'Budget Changes' column to their custom reporting view. See Set Up a Budget View for Custom Reporting.
-
- Company and Project level Reports.
-
Budget modifications are removed.
-
Budget changes are NOT supported by your existing Company and Project level reports.
Important
-
To preserve your historical budget modifications data, always download a copy of your reports before performing this migration.
-
If you have legacy reports that contain budget modification data, please note that you will need to recreate those reports if you want them to include budget changes. To quickly re-create those reports after the migration, it is recommended that you download your existing report(s) to use as a reference.
-
-
-
Procore Analytics
-
Budget modification dashboards will be hidden.
-
Budget changes dashboard will show historical data.
Important
- To update a custom Procore Analytics report after migrating your data, see Update a Custom Report When Migrating from Budget Modifications to Budget Changes.
-
How will data from my existing budget modifications show up in budget changes after migration?
Budget Modification Field (Legacy) | Budget Change Field (New) |
To: Budget Code | Budget Change Adjustment # FROM Budget Change Adjustment Allocation Line Item |
From: Budget Code | Budget Change Adjustment # TO Budget Change Adjustment Allocation Line Item |
Notes | Comments field on the FIRST Budget Change Adjustment Line Item. Comments are not available on Budget Change Adjustment Allocation Line Items (subsequent line items). |
Name: N/A (Field not available in legacy experience) | Name: 'Budget Change from Budget Modification Migration [ID Number]' |
Description: N/A | Description: "Budget Change created from Budget Modification on [MIGRATION DATE/TIME]. Budget Modification originally created on [CREATION DATE/TIME]. Migration authorized by [ADMIN USERNAME]." |
Change Event Line Item Association | Only budget modifications that are already associated with a change event line item will be connected to that change event line item as budget changes. No new associations will be created during the migration process. |
Change Event Creation | New Change Events will NOT be created from Budget Modifications that do not have change event line item associations. |