Copy/Move Project

En Français

This feature enables customer success to seamlessly copy or transfer projects between organizations or create duplicates within a single organization for better project management. Whether restructuring after a company acquisition or split or facilitating a handoff from a General Contractor to an Owner, this functionality ensures smooth transitions and proper project organization.

Copying a project may be necessary in various situations, ensuring a smooth transition, organization, or continuity of work. One common use case is project hand-off, where a project is moved or copied from a general contractor’s organization to the owner’s organization. In cases of company acquisition, projects from the acquired company may need to be transferred to the main company to consolidate operations. Conversely, during a company separation or division, one company may retain its projects while others are moved to the newly formed entity. Additionally, project phasing within the same organization may require duplicating a project under a different name. However, this process copies everything—including all items and historical data—which means that certain elements, such as approved Daily Reports, cannot be deleted. Understanding these scenarios helps ensure the correct handling of projects while maintaining data integrity and compliance.

What to Know

IMPORTANT

Only customer success can move or copy a project. To request this, please reach out to the customer success team for assistance.

• Single copy/move at a time: The same Source Project can be copied to two locations.

• Data sync required: Users must sync their data before copying/moving; unsynced data will not transfer and may be lost.

• No project re-combination: Copying creates diverging data, not a 2-project sync; after the Transition Start Date, users must coordinate updates.

• Source Project deletion: If moved, the original project is deleted but retained according to data retention policies.

See below for instructions to:

Copy or Move Project Terms

Copied Data

What is NOT Copied or Moved?

Annotations FAQ

Copy or Move Project Terms

Here are key terms the Customer Success team will use when discussing your project copy or move. Understanding them will help you make informed decisions and select the best options for your company and the situation.

• Source Project: The original project before transfer.

• Destination Project: The project after being moved.

• Original Org: The organization housing the Source Project.

• Destination Org: The organization receiving the Destination Project.

• Transition Start Date: The date/time when the copy process begins.

• Transition End Date: The date the Destination Project becomes active in the Destination Org.

Copied Data

The Copy Project function ensures that all relevant project data is transferred seamlessly from the Source Project to the Destination Project. This includes users, documents, folder structures, issues, workflows, and historical data. Below is a detailed breakdown of the copied components and how annotations are handled.

ll project data is included in the copy process, ensuring consistency and integrity. This includes, but is not limited to:

Users

• All users from the Source Project are copied to the Destination Project.

• Each user retains the same role they had in the Source Project.

Documents & Folder Structure

• Documents, folder structures, permissions, and markups are copied.

Issues

• All project issues are transferred as they existed in the Source Project.

Daily Reports

• Approved and pending Daily Reports are copied over.

Workflows

• All active and completed Workflows are duplicated in the Destination Project.

History

• The full history of items is copied.

• The original user actions remain unchanged, ensuring historical accuracy. This differs from previous move functions, which altered historical data.

Settings

• All project-specific settings are carried over to the Destination Project.

What is NOT Copied or Moved?

Statistics

• Stats are not moved or copied.

• On the Transition End Date, statistics will start collecting for the Destination Organization.

• For copied projects: The Source Project will not collect statistics between the Transition Start and End Dates.

• For moved projects: Since the Source Project is deleted, statistics will no longer be available.

• Event Logs:

  • Destination Project: “Project copied from Project Name (Original Organization)”

  • Source Project: “Project copied from Project Name (Original Organization) to Project Name (Destination Organization)”

Deleted Items

• Any items deleted in the Source Project before the copy/move process will not be transferred.

Export Table & Links

• The export table is not copied/moved.

• For moved projects:

  • Old links to exports/reports become useless once the Source Project is deleted.

• For copied projects:

  • Links to exports/reports remain functional in the Source Project even during copying.

Pending User Invitations

• Any user invitations that were still pending at the time of the move/copy are not transferred.

Annotations FAQ

Public Annotations

• Public annotations are copied with attribution to the original creator.

Shared Annotations

• Shared annotations are copied and remain attributed to the original creator.

• They continue to be shared with the same users.

Public/Shared Annotations from Removed Users

• Annotations created by users who were removed prior to the move are still copied.

• They remain attributed to the original creator and continue to be shared with the same users.

Private Annotations from Removed Users

• Private annotations are copied and remain attributed to the original creator.  If they’re added back to

  the project later, they will have access to them.

• They are retained in the Destination Project.

Next Steps

If you need to move or copy a project, please reach out to our Customer Success Team. They are the only team authorized to process project transfers.

To request a project move or copy:

1. Prepare Your Request: Gather essential project details, including the Source Project Name, Destination Org, and preferred Transition Start Date.

2. Contact Customer Support: Submit your request via email, or designated communication channel.

3. Confirm Details: A Customer Success representative will verify your request and guide you through any additional steps.

4. Monitor the Transition: You will receive updates on the status of your project copy/move. Ensure all users sync their data before the transition to prevent data loss.

Related Articles

Projects