# The signed integrity report RhinoMove hands you at the end of a monday.com move

Canonical: https://www.taskrhino.ca/products/rhinomove/integrity-report/

> The signed integrity report RhinoMove hands you after a monday.com move: what it checks, what it leaves out, and a seal check you can try on an example.

*RhinoMove*

The RhinoMove integrity report is the signed document you get at the end of a monday.com data migration. It counts what was copied, checks values and files, and lists what was skipped or could not be done. Edit one number in the example below and the signature breaks.

Each move ends with a signed integrity report, and when your data is deleted you get a signed deletion certificate. Both carry a digital signature (Ed25519) that anyone can check against RhinoMove's public key. TaskRhino runs each move with RhinoMove: see [RhinoMove, the monday.com account migration tool](https://www.taskrhino.ca/products/rhinomove/).

![Share card: the RhinoMove integrity report for a monday.com move, an example report with a seal, and the Certified monday.com Partner badge.](https://www.taskrhino.ca/_astro/rhinomove-integrity-share-card.DexUHTO__Z1kT431.jpg)

Try the seal check

## Break the seal: edit the example report and check the signature

An integrity report carries a digital signature. Change anything in it and the signature no longer matches. Edit any value in the example below, then press Check signature. The report is made at the end of a move: see [how a RhinoMove move runs](https://www.taskrhino.ca/products/rhinomove/how-it-works/) for where.

Click any value to change it

Example, signed with a throwaway key

### RhinoMove integrity report example

Report id (example)

All numbers on this card are example values

BoardFoundCopiedCheckedSkipped

Sealed example. Change any value, then press Check signature.

With JavaScript off the check cannot run. The example is signed; changing any value would make the check say: does not match, the document was changed after it was signed.

Example public key, not RhinoMove's

`870fb927bac2e722a1b8c42c58f048cb04f7a162e4ea72c26368d6d6ccaa90e6`

A real RhinoMove report is checked against RhinoMove's public key, not this example key. This one was made for the demo and its private half was thrown away.

Download the report bundle and check it yourself, offline: one command verifies our signature and every file's checksum, with no RhinoMove server involved.

[Book a free call](https://www.taskrhino.ca/contact-us/?service=migration)

Free 30-minute call, no obligation: see RhinoMove on your own case and get a quote for your move.

## The report, part by part

1.  1
    
    ### Counts
    
    Counts come from RhinoMove's own map of every copied object (a full recount of both accounts is a command-line tool, not a screen).
    
2.  2
    
    ### Values
    
    A SHA-256 fingerprint of each writable value is compared with the copy read back; formula, auto-number, mirror and button columns are excluded, tags are compared by name and comments by presence.
    
3.  3
    
    ### Files
    
    Every file RhinoMove copies is fingerprinted with SHA-256, and the copy in your new account is downloaded again and compared with the original: every file when a project's files total up to 20 GB (the default), a 5% sample above that. Link files and files over 500 MB are listed, not copied.
    
4.  4
    
    ### What was skipped or could not be done
    
    Where monday.com's API cannot do something, RhinoMove lists it in the report instead of failing quietly. 3 quick retries, then 5 with backoff, then a Retry / Accept-loss list for the rest.
    
5.  5
    
    ### The signature
    
    The report carries a digital signature (Ed25519) that anyone can check against RhinoMove's public key. Download the report bundle and check it yourself, offline: one command verifies our signature and every file's checksum, with no RhinoMove server involved.
    
6.  6
    
    ### What you download
    
    Formats: PDF, objects.csv and a signed manifest.json.
    

The example card above is a picture of the idea, not a copy of a real report.

The whole tool, not only its report, is on the [RhinoMove overview](https://www.taskrhino.ca/products/rhinomove/).

## The report on screen, from a demo project

Formats: PDF, objects.csv and a signed manifest.json. Two screens from a demo project show what is in the report. Moving data into monday.com from another tool instead? See [data migration services](https://www.taskrhino.ca/data-migration/).

**Demo data.** The top of the report of a demo project: what was checked, how, and what is listed below.

**Demo data.** The per-board results of a demo project: old account count, new account count, matched, mismatched and match rate for each board.

## How RhinoMove checks counts, values and files

Items and subitems compared by content hash; every other object checked present; files re-downloaded and SHA-256-matched up to 20 GB per project, a 5% sample (at least 20) above that.

Three checks, each with its limit in the same row. The report lists what it did and what it did not do.

What the integrity report checks, how, and what it leaves out
| Check | How | What it leaves out |
| --- | --- | --- |
| Counts | Counts come from RhinoMove's own map of every copied object. | A full recount of both accounts is a command-line tool, not a screen. |
| Values | A SHA-256 fingerprint of each writable value is compared with the copy read back. | Formula, auto-number, mirror and button columns are excluded. Tags are compared by name and comments by presence. |
| Files | Every file RhinoMove copies is fingerprinted with SHA-256, and the copy in your new account is downloaded again and compared with the original. | Every file when a project's files total up to 20 GB (the default), a 5% sample above that. Link files and files over 500 MB are listed, not copied. |

A move between regions needs the same proof: see [moving a monday.com account from the US to the EU](https://www.taskrhino.ca/data-migration/monday-us-to-eu/).

## What the report leaves out

An honest report states what it does not prove. Items and subitems are compared by content hash; every other object is checked present, not compared. These are the other limits, each from the same wording as the checks above.

-   ### Values it does not fingerprint
    
    Formula, auto-number, mirror and button columns are excluded. Tags are compared by name and comments by presence.
    
-   ### Files it lists, not copies
    
    Link files and files over 500 MB are listed, not copied. Above 20 GB of files a 5% sample (at least 20) is re-downloaded, not every file.
    
-   ### Counts, not a second recount
    
    Counts come from RhinoMove's own map of every copied object. A full recount of both accounts is a command-line tool, not a screen.
    
-   ### Changes after the scan
    
    Doc edits are flagged, not synced; columns, groups or boards created after the scan are not carried.
    

**full run: 1,447 objects verified, 0 failed (tests on a monday.com API simulator, 24-25 Oct 2026).** In that full test run, 7 of 1,454 objects were skipped: 6 link files and 1 update (tests on a monday.com API simulator, 24-25 Oct 2026). They are test results, not customer results.

Moving boards between accounts? [Copying boards between two accounts](https://www.taskrhino.ca/data-migration/monday-account-to-account/) says what monday.com's own copier covers.

## When something did not copy

3 quick retries, then 5 with backoff, then a Retry / Accept-loss list for the rest.

1.  **3**quick retries
2.  **5**retries with backoff
3.  **List**a Retry / Accept-loss list for the rest

Where monday.com's API cannot do something, RhinoMove lists it in the report instead of failing quietly. Accounts for 41 documented monday.com API limits and quirks, from daily call limits to file links that expire after an hour (41 is a count from our notes; some are reported, not moved).

The signed report lists what was skipped on purpose.

Combining accounts is its own job: see [merging monday.com accounts](https://www.taskrhino.ca/data-migration/merge-monday-accounts/).

## The audit trail behind the report

-   ### A log that shows if it was changed
    
    The audit log is tamper-evident: append-only, each entry chained to the last with SHA-256.
    
-   ### Kept after your copies are deleted
    
    The integrity report and audit log are kept, after staged copies of your data are deleted by default 21 days after go-live.
    

TaskRhino, the [team behind RhinoMove](https://www.taskrhino.ca/about-us/), runs each move.

## The second document: the deletion certificate

An integrity report says what moved. When your data is deleted you get a second document.

### Integrity report

Signed at the end of the move, with a digital signature (Ed25519): what was copied, checked and skipped.

### Deletion certificate

When your data is deleted you get a signed deletion certificate that anyone can verify from its JSON.

Built to follow monday.com's Developer Terms: it never rotates IP addresses or tokens to get around limits, and staged copies of your data are deleted by default 21 days after go-live (never more than 29 days without your written consent). The integrity report and audit log are kept. (monday.com has not confirmed this in writing.)

What to ask any vendor about data handling is in [monday.com data security and compliance](https://www.taskrhino.ca/monday-com/data-security-compliance/).

## What to forward to your auditor

-   The signed integrity report.
-   The signed deletion certificate, once your data is deleted.
-   The list of what was skipped or could not be done, taken from the report.
-   The table of what the report checks and what it leaves out, from the integrity report page.

Signatures are checked against RhinoMove's public key (Ed25519). Read how a move runs in the [order of work](https://www.taskrhino.ca/products/rhinomove/how-it-works/).

Plain text, ready to paste into an email to your auditor.

No sign-up, no price and no trial: TaskRhino runs each move with RhinoMove.

## Bring your questions to a free call

TaskRhino runs each move with RhinoMove: see [RhinoMove, TaskRhino's own tool](https://www.taskrhino.ca/products/rhinomove/). A free 30-minute call, no obligation: see RhinoMove on your own case and get a quote for your move. Bring the questions your auditor will ask.

### Book a free call

### See RhinoMove on your own case

### Get a quote for your move

## Questions about the integrity report

Direct answers, in the words we can stand behind.

### What is in the integrity report?

The integrity report counts what was copied, checks values and files, and lists what was skipped or could not be done. Counts come from RhinoMove's own map of every copied object (a full recount of both accounts is a command-line tool, not a screen). Formats: PDF, objects.csv and a signed manifest.json. See [where the report fits in a move](https://www.taskrhino.ca/products/rhinomove/how-it-works/).

### Who signs it, and who can check it?

Each move ends with a signed integrity report, and when your data is deleted you get a signed deletion certificate. Both carry a digital signature (Ed25519) that anyone can check against RhinoMove's public key. Download the report bundle and check it yourself, offline: one command verifies our signature and every file's checksum, with no RhinoMove server involved.

### What does the report check, and what does it leave out?

The report checks counts, values and files, and it leaves out the columns and files listed on this page. A SHA-256 fingerprint of each writable value is compared with the copy read back; formula, auto-number, mirror and button columns are excluded, tags are compared by name and comments by presence. Counts come from RhinoMove's own map of every copied object (a full recount of both accounts is a command-line tool, not a screen).

### What happens if a record does not copy?

Where monday.com's API cannot do something, RhinoMove lists it in the report instead of failing quietly. 3 quick retries, then 5 with backoff, then a Retry / Accept-loss list for the rest.

### Are files checked?

Yes, with limits. Every file RhinoMove copies is fingerprinted with SHA-256, and the copy in your new account is downloaded again and compared with the original: every file when a project's files total up to 20 GB (the default), a 5% sample above that. Link files and files over 500 MB are listed, not copied.

### Can I change the report afterwards?

You can change a copy of any document, but then its signature no longer matches when it is checked. The seal check on this page shows it with an example key. A real report is checked against RhinoMove's public key (Ed25519).

### How is this different from counting items myself?

A hand count checks what you chose to look at. RhinoMove counts from its own map of every copied object (a full recount of both accounts is a command-line tool, not a screen). Items and subitems are compared by content hash and every other object is checked present. Files are re-downloaded and SHA-256-matched up to 20 GB per project, a 5% sample (at least 20) above that, with the limits listed on this page.

### Is the report the same as the deletion certificate?

No. The integrity report is signed at the end of the move, and the second document comes later. When your data is deleted you get a signed deletion certificate that anyone can verify from its JSON.

### Do I get the report if some items were skipped on purpose?

Yes. The signed report lists what was skipped on purpose. In the full test run, 7 of 1,454 objects were skipped: 6 link files and 1 update (tests on a monday.com API simulator, 24-25 Oct 2026).
