Hygraph
Docs
View as Markdown

#Copy an entry to another project

Copy a saved content entry into a different project you belong to, without leaving the entry you're working on. Hygraph saves a draft in the target project. It does not publish the copied entry.

If you want to make a copy of a content entry in the same project, you can duplicate the entry.

#Permissions

  • You must be a member of the project you're copying into.
  • You must have the Create new entries permission for the target model.

If the project or model you need does not appear, ask a project admin to add you to that project or to give you appropriate permissions.

#Steps

You cannot copy an entry to another project from a new, unsaved entry form, from assets, or from variants.

  1. Open a saved content entry.

  2. Click ⋯ (More actions) in the entry title bar, then click Copy to project.

  3. In Copy entry to another project, choose:

    • Project: Other projects you belong to. The project you're in is not listed.
    • Environment: If the project has multiple environments, select the environment you want to copy the entry to.
    • Model: Models in that project's environment where you can create entries. Every model you can create in is listed, even if the fields do not match.
  4. Click Continue. After you click Continue, one of the following happens:

    The entry is copied and saved

    Hygraph saved a draft in the other project. You'll see Entry copied to target project name as a draft. Click Open entry to review it.

    If the target project has a content freeze, Hygraph still saves the draft. The entry is read-only until an admin lifts the freeze.

    Copy and save an entry to another project
    The entry is saved, but some content was skipped

    Hygraph saved a draft and lists what it left out. Some examples:

    • Links to other entries (references). Those entries live in the original project, so the links cannot come across. Reconnect them in the target project if you need them.
    • Rich text that includes embedded entries. The written text is copied, but the embeds are left out, because those entries live in the other project. If the target field does not allow those embeds at all, Hygraph blocks the copy instead.
    • Languages the other project does not have, or languages you're not allowed to edit there.

    What you can do: Open the draft, fill in anything missing, reconnect references, and save. You do not need a schema change for skipped references or languages that already exist in the target project. Ask a developer or project admin if a language you need does not exist in the target project, or you cannot edit a language you should be able to edit.

    If the target project has a content freeze, Hygraph still saves the draft. The entry is read-only until an admin lifts the freeze.

    Copy and save an entry to another project, with some values skipped
    The entry is copied but not saved

    Matching worked, but the other project rejected the save. Click Continue in target project name to open the new entry form with the copied values already filled in.

    Common reasons for the save failure, and who can fix them:

    What happenedCan you fix it?
    A required field is empty (including a required field the original entry did not have, or a required link that was skipped)Fill in the field in the other project and save.
    A value that must be unique, such as a title or slug, is already used by another entry in that projectChange the value and save.
    The value does not meet a field rule, such as lengthIf you can edit the field, change the value and save. Otherwise ask an admin.
    A content freeze is on in the target projectThe form can open, but you can only save after an admin lifts the freeze.

    If Continue in target project name does not open a tab, allow pop-ups and try again.

    Copy an entry to another project, but the save fails
    The entry is not copied

    Hygraph opens Can't copy this entry, with Schema doesn't match: the entry cannot be copied to that model because some fields do not match.

    You cannot fix this in the content form. Click Back and try a different model, or ask your developer or project admin to align the models (same field API IDs, types, list vs single, and localize settings). If you used the wrong model by mistake, pick another one yourself.

    Share copy rules with your developer or project admin. It lists exactly which field options need to match, so they don't have to reverse-engineer it from the field list.

    After the schema is updated, run Copy to project again.

    The entry cannot be copied due to schema mismatch

#What this does not do

  • Copy into the same project. Use Duplicate content.
  • Copy assets or variants.
  • Publish the new entry.
  • Copy linked entries, assets, or the schema along with the content.
  • Copy remote fields.
  • Merge into or overwrite an existing entry in the other project.

#What's next