Switch without starting over

Bring what you already have. For each tool: the steps, what comes over, and what stays behind.

GrapeLink

From Linktree to GrapeLink

  1. In GrapeLink, start on an empty page and choose "Bring my links" in the quick start.
  2. Paste the address of your public Linktree page.
  3. Untick what you don't want, then add the rest in one go.

What comes over

  • Your social profiles, by @handle
  • Your main links

What stays behind

  • Anything Linktree doesn't show publicly

Good to know

  • Best effort: Linktree sometimes refuses the request. Then you type your links in, it only takes a minute.

MangoForm

From Typeform to MangoForm

  1. Copy the public link of your Typeform, the one your respondents open.
  2. In MangoForm, start the import from Typeform on the dashboard and paste the link.
  3. The form opens as a draft in the editor, with a list of what didn't come over. Check it, then publish.

What comes over

  • Questions and their choices
  • Which questions are required
  • Descriptions
  • Question groups, as pages

What stays behind

  • Question types MangoForm does not have; the draft lists each one
  • AI follow-ups and Calendly blocks
  • Logic jumps and hidden fields: set them again in MangoForm
  • Images
  • The responses you already collected (they stay in Typeform)

Good to know

  • Best effort: the import reads the public form page, so a form Typeform doesn't show publicly can't be read

MangoForm

From Google Forms to MangoForm

  1. In Google Forms, click Send, then the link icon, and copy the link. The form must be public: no Google sign-in.
  2. In MangoForm, click "Import from Google Forms" on the dashboard and paste the link.
  3. The form opens as a draft in the editor, with a note on anything that didn't come over. Check it, then publish.

What comes over

  • Questions and their options
  • Which questions are required
  • Sections, as pages
  • Time questions
  • Shuffled option order

What stays behind

  • Images and videos
  • Response validation and logic
  • The responses you already collected (they stay in Google Forms)

Good to know

  • Tick-box grids come over as one answer per row

PeachCalendar

From Calendly to PeachCalendar

  1. In PeachCalendar, open "Import from Calendly" ("Moving from Calendly?" on the dashboard).
  2. Paste your public Calendly link.
  3. Untick the event types you don't want, import the rest, then set your availability in PeachCalendar.

What comes over

  • Your event types: name, duration, description, colour and location

What stays behind

  • Bookings
  • Availability (you set it in PeachCalendar)
  • Integrations

Good to know

  • Best effort: Calendly may not answer. Then you create your event types by hand.

GuavaTeam

From Trello to GuavaTeam

  1. In Trello, export the board as JSON.
  2. In GuavaTeam, click "Import from Trello" on the dashboard.
  3. Choose the file, check the preview, then import. One board at a time.

What comes over

  • Lists and cards
  • Card descriptions and due dates
  • Labels and checklists

What stays behind

  • Archived lists and cards
  • Attachments
  • Comments
  • Members

KiwiProof

From Senja to KiwiProof

  1. In Senja, export your testimonials as a CSV file.
  2. In KiwiProof, open a space, then "Switch from Senja or Testimonial.to".
  3. Pick Senja, choose the file and check which column goes where.
  4. Check the preview, then save.

What comes over

  • The testimonial text and its author
  • The original date of each testimonial
  • Any other CSV too: you pick the columns

What stays behind

  • Photos and hosted videos (a video can be a YouTube or Loom link)

Good to know

  • Nothing is saved before the preview, and duplicates are skipped
  • They arrive pending: nothing shows on your wall until you approve it

KiwiProof

From Testimonial.to to KiwiProof

  1. In Testimonial.to, export your testimonials as a CSV file.
  2. In KiwiProof, open a space, then "Switch from Senja or Testimonial.to".
  3. Pick Testimonial.to, choose the file and check which column goes where.
  4. Check the preview, then save.

What comes over

  • The testimonial text and its author
  • The original date of each testimonial
  • Any other CSV too: you pick the columns

What stays behind

  • Photos and hosted videos (a video can be a YouTube or Loom link)

Good to know

  • Nothing is saved before the preview, and duplicates are skipped
  • They arrive pending: nothing shows on your wall until you approve it

KiwiProof

From Google reviews to KiwiProof

  1. Export your Google Business Profile reviews with Google Takeout, or copy them one by one.
  2. In KiwiProof, open a space, then "Import Google reviews".
  3. Upload the Takeout export or paste a review, check it, then save.

What comes over

  • The reviews customers left on your Google Business Profile

What stays behind

  • New reviews: they don't arrive by themselves, you bring them in again when you want them

DurianStatus

From Statuspage to DurianStatus

  1. In DurianStatus, open "Switch from Statuspage" in the dashboard.
  2. Paste the address of your public Statuspage page and check the preview.
  3. You get a draft page. Check it, add your monitors, then publish when ready.

What comes over

  • Your components
  • Incidents and maintenances from the last 90 days

What stays behind

  • Subscribers
  • Monitors (you add the checks in DurianStatus)
  • Logo, favicon and colours
  • History older than 90 days
  • Components that are only links

Good to know

  • Only public Statuspage pages can be read

LimeQR

From another QR code tool to LimeQR

  1. Export your codes' destinations as a CSV file from the tool you use now.
  2. In LimeQR, open Import ("Import from CSV").
  3. Check the rows, create the codes, then download them as SVG files in a ZIP.

What comes over

  • Each code's destination, with an optional custom address and name
  • Up to 100 rows per file on Solo, 500 on Pro

What stays behind

  • Codes you already printed: they point to your old tool's links. LimeQR makes new codes, it can't take over the old ones
  • Scan history

FigVote

From Canny to FigVote

  1. Export your posts from Canny as CSV, or as JSON with Canny's API (the JSON includes comments).
  2. In FigVote, open Settings, then "Import from Canny", and choose the file and the board the posts go to.
  3. Check the preview of what will be written, then import.

What comes over

  • Posts, with their status (custom statuses become Open), tags and original dates
  • Vote counts, shown as "+N earlier"
  • Public comments, from the JSON export

What stays behind

  • Voters and authors
  • Images

Good to know

  • Nothing is saved before the preview; a second import skips the posts already there
  • Posts from private Canny boards go to a private board, or are left out

All 8 apps are in the bundle: $29 once.

See the bundle