You can do this manually by examining and copy/pasting the raw content where Chrome stores the flags, but you need root access.

The file that stores the flags is located on:

• /data/user/0/com.android.chrome/app_chrome/Local State (according to Chromium's Official Documentation)
• /data/data/com.android.chrome/app_chrome/Local State (based on testing and experience, possibly for single-account user)

The file Local State (without extension) is in a JSON format, which is actually a normal text-file and can be opened with any text editor with root access (Root Explorer includes text editor, but it's not free).

Thanks to Synetech's answer on Super User, the flags are stored under enabled_labs_experiment JSON array in browser JSON object node.

Example (taken from the answer)

{
  …
  "browser": {
    "enabled_labs_experiments": [ "disable-gpu-vsync", "extension-apis", … ],
    …
  }
  …
}

It's possible to do this manually by examining and copy/pasting the raw content where Chrome stores the flags, but root access is needed.

The file that stores the flags is located on:

• /data/user/0/com.android.chrome/app_chrome/Local State (according to Chromium's Official Documentation)
• /data/data/com.android.chrome/app_chrome/Local State (based on testing and experience, possibly for single-account user)

The file Local State (without extension) is in JSON format, which is actually a normal text file and can be opened with any text editor having root access (Root Explorer includes text editor, but it's not free).

Thanks to Synetech's answer on Super User, the flags are stored under enabled_labs_experiment JSON array in the browser JSON object node.

Example (taken from the answer)

{
  …
  "browser": {
    "enabled_labs_experiments": [ "disable-gpu-vsync", "extension-apis", … ],
    …
  }
  …
}