Move to Formfeed

What a migration involves, per product: what the importer takes over, what it reports, and what changes in your code.

The same three steps every time

1. 1Import the templates, straight from your account with the old provider or from an export. The importer inlines the partials, snippets and child templates an API render cannot reach, and reports every filter or setting it could not map, with the line it is on.
2. 2Compare the output. Render both sides with a test key, which is not metered, and put the PDFs side by side before a customer sees one.
3. 3Swap the key and the base URL. Where Formfeed has compatibility endpoints for your old provider, they take the request shape you already send, so the first step can be a base URL and nothing else.

• apitemplate.ioImport your Jinja2 templates with a diagnostics report, keep your integration running through the compatibility endpoints, and switch to EU rendering in an afternoon.

  Formfeed as an apitemplate.io alternative →

• PDFMonkeyImport your Liquid code templates with your PDFMonkey API key. Dates, number formats, snippets and settings are converted, and the report shows the rest with the line.

  Formfeed as a PDFMonkey alternative →

• jsreportImport Handlebars templates from a jsreport export with their assets, child templates and chrome-pdf settings, and stop running a report server.