---
title: "Copy all BE-groups and cards from one project to another"
description: "Users can now copy all BE-groups and cards from one project to another in one action - instead of having to copy each card individually through the card view. Before: Users had to open each BE-card separately and select \"Copy…"
url: "https://help.ajoursystem.com/en/docs/copy-all-be-groups-and-cards-from-one-project-to-another/"
updated: "2026-10-22"
category: AjourFm
---

# Copy all BE-groups and cards from one project to another

Users can now copy all BE-groups and cards from one project to another in one action - instead of having to copy each card individually through the card view.



Before: Users had to open each BE-card separately and select "Copy BE-card" After: The "Copy from" button on the BD-board does it all at once



How it works



1. Navigate to the BD-board in the destination project (the project you want to import to)



2. Click the "Copy from" button



3. Select the source project in the drop-down menu



4. Confirm - all BE-groups and cards are imported



Important limitations and requirements



Prerequisites




The BD-board must be empty (no BE-cards may exist yet)



The user must have the project permission Ajour FM - Create



The destination project must be able to accept all BE-groups from the source




What is NOT copied



The following fields are NOT imported:




Installation date



Warranty start date / end date



Operation start date



Warranty responsible (person + company)



Operation responsible (person + company)



Attached files and documents



Comments




This is intentionally designed this way - these fields are project- or construction-specific.



✓ What CAN be copied




BE-card structure and data



Maintenance elements (maintenance components)



Supplier information



The entire BE hierarchy




Important technical details



BE-groups and templates




The system supports templates: SFB, FVK and user-defined



If you copy from an SFB project to an FVK project, the FVK project will be converted to the SFB template




Property groups




All property groups in the destination project must be empty



You can not mix imports between different property groups in the same operation



If the project has several property groups with cards, the import fails




Error handling



If the BD-board is not empty:




Error message: "Copy failed. The BD board must be empty."



A toast notification is shown - the dialog does not open




When should this function be used?



Perfect for:




Setting up new projects based on existing templates



Standardising the FM structure across projects



Saving time when the same BE hierarchy needs to be repeated many times



Not for:



Migrating existing card data between projects (use export/import or manual copying of individual cards instead)



Merging data from several projects