Plannr lets you add Relationships and Dependants to your client records in bulk, so you don't have to create each one by hand. This guide explains how each import works, the fields you'll need, and what to expect when you run them.
How imports work
Both imports run through the same import wizard and use a CSV file. The wizard works in three stages, checking your file first so you can fix any problems before anything is saved:
Stage | What happens |
Validate | Plannr checks your file for errors before anything is saved, so you can correct issues up front. |
Create | Valid new records are created. |
Update | Existing records matched in your file are updated rather than duplicated. |
The created and updated dates on each record are set automatically to the date you run the import — you don't need to include these in your file.
Importing Relationships
Use this to link contacts to one another in bulk — for example spouse, business partner, or trustee — instead of adding each link manually.
What to know before you start
Each row captures both directions of the link — the relationship and its inverse — so Plannr creates both sides from a single row. You don't need a second row for the reverse.
The Relationships import currently supports these four columns:
Column | What it's for |
| The contact the relationship is from. |
| The contact the relationship is to. |
| The relationship label (for example, Spouse). |
| The reverse label, which Plannr uses to create the other side of the link. |
External reference columns (such as external reference value and source) are not yet supported for the Relationships import — only the four columns above are live.
Importing Dependants
Use this to add dependants — for example children — to your client records in bulk.
What to know before you start
A dependant can sit under more than one contact — for example a child linked to both parents. Use
account_uuidsto set which accounts it links to.uuidis only used when updating an existing dependant. Leave it blank when creating a new one — the dependant doesn't exist yet, so there's nothing to match on.
The Dependants import uses these columns:
Column | What it's for |
| The dependant's unique ID. Only needed when updating an existing dependant; leave blank when creating a new one. |
| The dependant's first name. |
| The dependant's last name. |
| A preferred or familiar name, if different from their first name. |
| The dependant's relationship to the account (for example, Son or Daughter). |
| The dependant's date of birth. |
| Whether the dependant is financially dependent. |
| Free-text notes about the dependant. |
| The account(s) the dependant should be linked to. A dependant can be linked to more than one. |
There's a hard limit of 50 dependants per account. Once an account reaches 50, any further dependant rows for that account will fail — so split or trim your file accordingly.
Running an import
Prepare your CSV file with the correct column headers, filling in all required fields. You can download an example CSV from the imports page.
Upload your file and let Plannr validate it.
Review any rows flagged during validation and correct them in your file.
Re-upload, then confirm to create new records OR update existing ones.
Frequently asked questions
Frequently asked questions
Do I need to create both sides of a relationship?
No. Each row captures both the relationship and its inverse, so Plannr creates both sides of the link from a single row.
Can a dependant belong to more than one client?
Yes. A dependant can sit under multiple contacts — for example a child linked to both parents. Use the account_uuids column to set which accounts it links to.
Do I need a uuid when adding new dependants?
No. The uuid column is only used to match and update existing dependants. Leave it blank when creating new ones.
Is there a limit on dependants per account?
Yes — there's a hard limit of 50 dependants per account. Rows that would take an account beyond 50 will fail.
What file format should I use?
Both imports use a CSV file through the same import wizard.
How do I know which fields are required?
Run the import and review the Validate step — Plannr flags any rows missing required fields so you can correct them before any records are created.
What happens to records that already exist?
Existing records matched in your file are updated rather than duplicated, as part of the standard Validate / Create / Update process.