download dots

📤 Import Customer Data Without Losing Any

Turn the app you built for yourself into something other people pay to use. These prompts add the parts that make a tool into a product: customer sign-in, plans and trials, limits that mean something, a billing lifecycle that handles the awkward cases, and an admin view so you can see who is actually using it. The unglamorous half nobody enjoys assembling.
  • Tested prompts
  • Edit for your use case
  • Works across models
  • Save in Taskade
Import Customer Data Without Losing Any

Copy

New customers cannot move to my product because their data is somewhere else. Build me an import tool. A customer uploads a file, and the app shows the columns it found and suggests which field each one maps to, which they confirm or change. Before anything is written, show a full preview of what will be created, what will be updated, and what cannot be imported and why, row by row. Only on confirmation does anything get written, and a partial import is allowed with a clear report of the rows that failed. Keep the original file and the import record so it can be reviewed, re-run or reversed. Add an AI agent that guesses the column mapping from the data itself, explains each error in plain language a non-technical person can act on such as this date is in an unclear format, and suggests the fix. Automate a notification when an import finishes with a summary, and a scheduled reminder if a customer started an import and never confirmed it. Two logins: a customer who imports into their own account only, and an owner who can see all imports and help.

STATUS · LIVE
v1

01 / Spark - intelligence awakens

Import Customer Data Without Losing Any

Let customers import their existing records with column matching, a full preview, row-level errors, and a safe partial import.

// the spark catches · intelligence awakens · the answer unfolds

The hardest part of switching to your product is moving the data. A good import is a conversion feature, not a technical one, and a preview is what makes people trust it.

What's Included

  • Column matching the customer confirms rather than guesses at.
  • A preview before anything is written which is what builds confidence.
  • Clear errors by row rather than one failure message.
  • An assistant that guesses the mapping and explains each problem.

How To Use

  1. Always preview before writing. An import that cannot be checked is not trusted.
  2. Report errors row by row so they can be fixed, not just counted.
  3. Let a partial import succeed and report what did not.
  4. Keep the original file so an import can be re-run or undone.

Follow it with onboarding, and record it in the audit trail.