> This page is for RakeSign.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.cloudraker.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.cloudraker.com/_mcp/server.

# Move from Paperwork signing

Use `/v1/signing` for new product integrations.
It exposes RakeSign documents, templates, consent, webhooks, and administration through one product surface.

`POST /v1/sign` remains available for existing Paperwork callers.
Its request body, response shape, run URLs, retention rules, and signing behavior remain compatible.
Existing runs continue through their current endpoints.

## Compare the workflows

| Existing Paperwork workflow             | RakeSign workflow                                        |
| --------------------------------------- | -------------------------------------------------------- |
| Organization API key                    | Scoped key for one managed team                          |
| `POST /v1/sign` with a file and signers | Create a document, add a PDF, then send                  |
| `GET /v1/runs/:id`                      | `GET /v1/signing/documents/:id`                          |
| Run envelope and audit routes           | Document progress, PDF, and audit routes                 |
| Paperwork webhook subscriptions         | Team-scoped RakeSign event subscriptions                 |
| Legacy template delegation scope        | Consent for a saved RakeSign template revision           |
| Run-based integration records           | Shared RakeSign document records with integration origin |

Both paths use the same signing engine.
They retain different resource contracts so existing integrations can continue.

## Migrate new work

1. Create a RakeSign integration key for the target team.
2. Select only the required [permissions](/rakesign/developers/authentication).
3. Create or save templates in that team when the integration needs reusable documents.
4. Implement the [document workflow](/rakesign/developers/documents).
5. Register [RakeSign webhooks](/rakesign/developers/webhooks) and verify their payloads.
6. Route new requests to RakeSign after your integration checks pass.

Keep polling existing Paperwork runs through their original URLs until they finish.
Do not resubmit an in-flight document to RakeSign as a migration step.
That would create a separate signing request.

## Keep existing records

The migration does not import old runs into RakeSign automatically.
Existing Paperwork runs do not gain team visibility or RakeSign document IDs.
Their retention and access rules remain unchanged.

RakeSign keys cannot call the legacy `/v1/sign` route.
Keep the existing credential for legacy work until that work finishes.

## Recreate delegation scope

Create a saved RakeSign template and request consent for its current revision.
Do not copy an old consent status into a new grant.
The signer must accept the new revision-bound request.

Read [standing delegation](/rakesign/developers/delegation) before enabling delegated sends.