Migrate From Canopy to Remindoo
Moving from Canopy depends on which modules you licensed. Client records and contacts export and import; workflows, document structures and module-specific data need rebuilding. Firms usually migrate module by module rather than all at once.
Moving from Canopy depends on which modules you licensed. Client records and contacts export and import; workflows, document structures and module-specific data need rebuilding. Firms usually migrate module by module rather than all at once.
Last updated: September 2026
What is involved in moving from Canopy?
Canopy's modular design shapes this migration. A firm using only the client record and documents has a much simpler move than one using documents, workflow, time and billing together, and the plan should reflect which of those you actually turned on.
Start by listing the modules you are licensed for and, separately, the modules you genuinely use. In most firms those two lists differ, and the second one is the one that has to be rebuilt.
Document structure deserves specific attention. Canopy's folder and file organization is often deeply embedded in how staff work, so decide your new structure before exporting rather than recreating a structure you already dislike.
What moves and what does not
Readable text in every cell. Where something has to be done by hand, the table says so rather than implying an automatic transfer.
| Item | How it moves | What to watch |
|---|---|---|
| Client records and contacts | Exports and imports | Verify entity types and primary contacts |
| Documents and folder structure | Manual export and upload | Decide the new folder convention first |
| Workflow templates | Rebuilt | Rebuild only the templates in active use |
| Open jobs and tasks | Manually recreated | Recreate live work only |
| Time entries | Exported for reporting | Start fresh from a cutoff date |
| Invoices and open balances | Exported; balances re-entered | Reconcile open items before the cutoff |
| Client portal access | New invitations | Batch the invitations by service line |
Accurate as at September 2026. Export options change, so confirm current capabilities with your existing vendor.
What has to be rebuilt?
These do not transfer from any system to any other, and pretending otherwise is how migrations slip.
- Recurring services for every workflow you actually run, with internal and external due dates.
- A document naming and folder convention, agreed before the first upload.
- Client request lists to replace module-driven document collection.
- Roles and permissions for preparers, reviewers and administrators.
- Reporting views for capacity and utilization.
How long does the migration take?
A realistic sequence for a firm that has agreed its process. Add time, not people, if that decision is still open.
Week 1: module audit
List licensed modules against modules in genuine use, and decide what has to exist in the new system on day one.
Weeks 2-3: export and import
Export clients, contacts, documents and time data. Import clients and audit a sample.
Weeks 4-5: rebuild
Build recurring services, request lists and permissions. Agree the document convention and upload current-year files.
Weeks 6-8: pilot and switch
Pilot one service line end to end, then move the remaining service lines in batches with read-only access retained on the old system.
Switching checklist
Work top to bottom. Nothing below the import line should start before a sample of imported records has been checked.
- Confirm contract end date and notice period.
- List licensed modules versus modules in use.
- Export clients and contacts to CSV.
- Export documents by client, current year first.
- Export time and billing data for records.
- Reconcile open invoices before the cutoff.
- Agree the new document naming convention in writing.
- Import clients and audit twenty records.
- Rebuild active workflows as recurring services.
- Pilot one service line end to end.
- Invite clients to the new portal in batches.
- Retain read-only access for one filing cycle.
Should you run both systems in parallel?
Yes, briefly, and with rules.
- Migrate by service line rather than all at once; it is the natural unit when the old system was modular.
- Run one full cycle of each service line before retiring the equivalent module.
- Keep read-only access until the last service line has completed one cycle.
What our team does
So you know exactly where the line is between our work and yours.
- We import your client list and contacts from a CSV or an export from your current system.
- We build your first three recurring services with you rather than handing you a blank template library.
- We set the internal and external due dates for those services so the first cycle runs properly.
- We stay with you through one complete cycle of your busiest recurring service before you are on your own.
Before you switch
Frequently asked questions
What can we export from Canopy?
Client and contact data export in standard formats, and documents can be downloaded. Workflow structures, module configuration and in-platform histories are rebuilt rather than migrated. Confirm current export options directly with Canopy.
Should we migrate everything at once?
Usually not. Because Canopy is modular, most firms move one service line at a time, complete a full cycle in the new system, then move the next. It takes longer overall but almost never leaves a service line stranded mid-cycle.
What happens to our document folders?
Folder structures do not transfer automatically. Agree a naming and folder convention before you export, upload current-year files into it, and keep older material in an archive rather than recreating years of structure.
How long should we keep Canopy access?
Keep read-only access through at least one full filing cycle after the last service line moves, so nobody has to guess what a prior-year job contained.
What does Remindoo do during the migration?
We import your client list, build your first three recurring services with you, set internal and external due dates, and stay with you through one complete cycle of your busiest service.
Planning a move from Canopy?
Book a call with your client count and service list, and we will map the migration against your calendar before you commit to anything.