12+ Insightly Best Practices From the Top 1% of Users
In our experience, Insightly best practices come down to clean data, tight permissions, and automation that matches how your team actually sells. The teams who get the most from Insightly treat it as a shared system of record, not a personal notebook, and they review it on a set schedule. Get those habits right and adoption, reporting, and forecasting all start to improve together.
Why teams trust our Insightly playbook:
Our 30 CRM specialists have tuned Insightly across 12 industries, backed by 250+ combined years of hands-on work. We stay vendor neutral, so every tip here fits your team, not a sales quota.
Want a second set of eyes on Insightly?
Reach out for a vendor-neutral review from a crew fluent in 14 CRM platforms. Our team can audit your data, roles, and workflows before small gaps turn into cleanup projects.
What Does an Insightly Best Practice Actually Mean?
An Insightly best practice is a repeatable habit that keeps your data clean, your team consistent, and your pipeline honest. It’s less about clever tricks and more about the routines the best teams never skip.
The strongest Insightly accounts we work with treat the CRM as one shared source of truth. Everyone logs the same way, so a record means the same thing to sales, support, and the founder.
That shared discipline is the real difference. Knowing where the tool shines and where it drags, which we cover in Insightly’s pros and cons, helps you build habits that play to its strengths instead of fighting them.
Here are the 12 practices that separate the best-run Insightly accounts from everyone else, in the order most teams should tackle them.
- Consistency: every deal follows the same stages and required fields.
- Ownership: each record has a clear owner and a next step.
- Restraint: they track what they’ll use, not every field on offer.
- Review: they audit the system on a fixed cadence, not in a panic.
Worth knowing: A best practice only counts if the whole team follows it. In our experience, one clean habit that everyone keeps beats five smart rules that only the admin remembers, because a CRM lives or dies on the record nobody skipped.
Best Practice #1: Set Your Pipeline Stages and Core Fields Before You Import a Single Contact
Spend your first week on setup and habits, not features. Get your pipeline stages, key fields, and a few core reports right before anyone imports a single contact.
We’ve seen new teams rush the import and pay for it later. A tidy start saves you the cleanup that eats week three.
This short order of operations works for most teams. Pairing it with structured Insightly training in the same week helps the habits actually stick.
Why the First Friday Review Matters Most
That first weekly review sets the tone for everything after. If the team sees the founder actually reading the pipeline, they log properly the next week.
Skip it once and the habit slips fast. A standing 20-minute review is the cheapest adoption tool you have.
Best Practice #2: Run a Duplicate Check Every Month and Make Deal Fields Required to Save
Clean data is the foundation every other best practice sits on. If contacts are duplicated and fields are half filled, your reports lie and your team stops trusting the system.
Good hygiene is mostly about rules you set once and enforce. Deciding which fields matter, and matching that to Insightly’s features, keeps the record light and useful.
These are the rules we set on almost every account we touch.
| Field type | Hygiene rule | Why it matters |
|---|---|---|
| Contact email | Required and unique | Blocks duplicates and broken automation |
| Deal stage | One owner sets it, no free text | Keeps forecasts honest |
| Company name | Standard format, no abbreviations | Stops split reporting on one client |
| Close date | Always in the future when open | Prevents dead deals hiding in the pipeline |
Why Duplicate Contacts Quietly Cost You the Most
A duplicate contact splits one buyer’s history across two records, so half the interactions never show up where the team looks for them. That gap makes a well-served client look neglected, and a rep ends up chasing someone who already replied.
Run a duplicate check monthly, not yearly. Across our projects, a large share of the messy pipelines we audit trace back to two records for the same buyer.
Pro tip: Make required fields do the heavy lifting. If a rep cannot save a deal without a stage and a close date, most of your hygiene problems solve themselves before a monthly cleanup ever runs.
Best Practice #3: Run Your Weekly Pipeline Meeting Off the Dashboard to Drive Logins
The fastest way to drive daily logins is to run your weekly pipeline meeting straight off the Insightly dashboard. When the numbers that decide the meeting live only in the CRM, reps keep them current without being nagged.
Low logins are usually a design problem, not a discipline problem. Research from Vantage Point found that weak user adoption alone accounts for 38 percent of failed CRM projects, which lines up with what we see when a rollout stalls.
Strong adoption is also what turns the tool into real Insightly ROI, since an empty CRM returns nothing.
Two Ways to Drive Daily Logins
You can pull people in with value or push them in with rules. The best teams lean on the first and use the second only where it’s genuinely needed.
- Put the leads and next steps reps need inside one saved view.
- Automate reminders so nobody tracks follow-ups in their head.
- Show wins in the dashboard so effort is visible.
- Run pipeline meetings only from Insightly, never from a spreadsheet.
- Require deals to live in the CRM before they count toward quota.
- Make the weekly review the single source of pipeline truth.
From the field: When a founder runs the Monday meeting straight off the dashboard, login rates climb within two weeks. In our experience, that one change does more for adoption than any training session.
Best Practice #4: Start Every Role With Tight Access and Review Admin Rights Each Quarter
Set permissions so people see what they need and nothing they don’t. Loose access feels friendly early on and turns into a data risk as you grow.
Start tight and open up as roles prove they need more. Getting this right also feeds into Insightly security, since most leaks start with over-broad access, not a hacker.
| Role | Access level | Typical example |
|---|---|---|
| Rep | Own records and shared pipeline | Field sales, account managers |
| Manager | Team records and reports | Sales lead, support lead |
| Admin | Full setup and permissions | Ops owner, systems admin |
| Viewer | Read only on set reports | Finance, leadership guests |
Review who has admin rights every quarter. We’ve walked into accounts where half the team could delete records, and none of them knew it.
Best Practice #5: Cap Your First Automation Build at Four or Five Documented Workflows
Automate the boring, repeatable steps first and leave judgment calls to people. Good automation removes busywork without hiding what’s happening.
The trap is automating too much too soon. Layering smart features, including Insightly AI, only pays off once your stages and fields are already clean.
These are the automations we turn on for most teams, in roughly this order.
- Lead routing: assign new leads to the right owner instantly.
- Follow-up tasks: create the next step when a stage changes.
- Stale-deal alerts: flag deals with no activity in two weeks.
- Handoff triggers: notify support when a deal closes won.
Where Automation Usually Goes Wrong
Most broken automations trace back to a renamed field or a skipped stage that a rule quietly depended on. The workflow keeps running, just against the wrong trigger, so nobody notices until a customer falls through.
Document every workflow you build in one place. An automation nobody remembers becomes the ghost rule that breaks a report six months later.
Keep in mind: Every automation is a rule someone has to maintain. We usually cap a first build at four or five workflows, because a lean set that everyone understands beats a clever web nobody can debug.
Best Practice #6: Build Only the Three Dashboards Your Weekly Meeting Actually Uses
Build reports around the decisions you actually make, not around every number you can pull. A dashboard should answer a question in one glance.
Most teams need fewer reports than they think. Advanced reporting sits on higher tiers, so it’s worth checking Insightly pricing before you promise leadership a view your plan can’t build.
The Three Dashboards Most Teams Really Need
- Pipeline health: open deals by stage and age.
- Activity: calls, emails, and tasks per rep this week.
- Forecast: weighted value by expected close date.
Who Should Own Each Dashboard
Pipeline health belongs to whoever runs the weekly sales meeting, since it drives that conversation directly. Activity and forecast fit better with a manager who compares them week over week rather than a rep who only checks their own numbers.
Give every dashboard an owner who checks it weekly. A report nobody reads is just clutter that slows the page down.
Best Practice #7: Build Your Insightly Rollout in Three Phases So the Team Keeps Up
Roll out in phases so people learn one thing at a time. A big-bang launch overwhelms reps and buries early problems under too much change.
Smaller teams can move faster, and our notes on Insightly for startups lean into that. Larger teams should slow down and stage the work.
Phase 1: Core Setup
Lock in your pipeline, fields, and permissions with a small pilot group. Fix what breaks here, where the blast radius is tiny.
Phase 2: Team Onboarding
Bring in the wider team once the basics are proven. Train them on the two or three actions they’ll do every day, not the whole product.
Phase 3: Automation and Reporting
Add workflows and dashboards only after people log in reliably. Automating a habit nobody has yet just breaks in new ways.
Reality check: The playbook says onboard everyone at launch, but almost no team is ready for that. A staggered rollout over three or four weeks tends to stick far better than a single training day that reps forget by Friday.
Best Practice #8: Connect Only the Integrations That Carry Real Data and Give One Person the List
Connect only the tools you truly need and document each one. Every integration is a moving part that can break when either side updates.
Start with the connections that carry real data, like email and accounting. Our rundown of Insightly integrations shows which ones most teams lean on first.
- Keep a simple log of what’s connected and who owns it.
- Test each integration after any major update on either tool.
- Send data one direction where you can, to avoid sync loops.
Assign one person to own the integration list. When a sync breaks quietly, someone needs to notice before bad data spreads.
Best Practice #9: Turn On Two-Factor for Every User and Pull Access on Someone’s Last Day
Security best practice is mostly good housekeeping done consistently. Strong passwords, two-factor login, and tight roles stop the vast majority of problems.
Compliance matters more in some fields than others. Teams handling sensitive records, like those in our guide to Insightly for nonprofits, need clear rules on who can export data.
- Turn on two-factor authentication for every user, no exceptions.
- Limit who can export or delete records to a short list.
- Remove access the same day someone leaves the team.
Heads up: Offboarding is where most CRM data quietly walks out the door. Pulling access on someone’s last day, not a week later, closes the single most common gap we find during a security review.
Best Practice #10: Name a Respected Team Champion and Fix the Top Complaints in Month One
Change management is the people side of a rollout, and it decides whether the setup sticks. The tool can be perfect and still fail if the team never buys in.
Explain the why before the how. People adopt a system they understand and quietly resist one that feels dropped on them.
Name a Champion on the Team
Pick someone respected who can answer day-to-day questions. A local champion gets more done than an admin the team barely sees.
Collect Feedback in the First Month
Ask reps what feels clunky and fix the top few things fast. An early fix proves the system is theirs, not something imposed on them.
One caveat: Change fatigue is real. If you’ve just moved tools twice, hold off on big new workflows for a month so the team can catch its breath before you ask them to learn one more thing.
Best Practice #11: Test Every Change on Dummy Records Before It Touches Live Data
Test every meaningful change on a small scale before it hits the whole team. A quick check on a few records saves you from breaking live data.
This matters most for automation and integrations. If you’re building against the Insightly API, run calls on test records first so a bad mapping never touches real customers. Insightly’s own developer documentation caps calls at 10 requests per second, and it returns an error the moment a script crosses that line, so it pays to check your call volume before a bulk test goes live.
- Build the change and try it on a handful of dummy records.
- Watch one full cycle to confirm nothing fires twice.
- Roll it out to one team before the whole company.
Keep a short changelog of what you altered and when. When something breaks, that note turns a two-hour hunt into a two-minute fix.
Best Practice #12: Audit Your Setup for the Five Habits That Quietly Skew Your Reports
A quarterly audit of your setup catches the five habits that quietly skew your reports before they harden. Each one below is cheap to fix early and expensive to unwind once it spreads.
When these pile up, teams often blame the tool and start weighing Insightly alternatives before checking their own habits. Fix the habits first.
How Do You Run an Insightly Best-Practice Health Check?
A health check is a scheduled audit of your data, roles, and workflows. Run one every quarter and you catch drift before it becomes a rebuild.
Keep it simple and repeatable. If the check surfaces recurring errors, our notes on troubleshooting Insightly errors help you sort a quick fix from a real one.
| Area | What to check | How often |
|---|---|---|
| Data | Duplicates and blank required fields | Monthly |
| Access | Who holds admin and export rights | Quarterly |
| Workflows | Rules still firing as intended | Quarterly |
| Reports | Dashboards still used and accurate | Quarterly |
What a Health Check Catches That Daily Work Misses
Day-to-day work only shows you the record in front of you, so a rep never sees that ten other deals share the same stale close date. A scheduled check looks across the whole base at once, which is the only way that kind of pattern surfaces.
Quick win: Put the health check on the calendar as a recurring event with an owner. In our experience, the audit that has a name and a date attached actually happens, while the one people mean to do never quite does.
What Are the Signs Your Insightly Setup Needs a Cleanup?
The clearest sign is that people stop trusting the numbers. Once reps keep their own side spreadsheet, your CRM has quietly stopped being the source of truth.
Don’t rush to switch tools when this happens. Plenty of teams compare Insightly vs HubSpot when the real problem is a setup that drifted, not the software.
- Reports disagree with each other on the same question.
- The same client shows up under two or three records.
- Half your custom fields sit empty across most deals.
- Nobody can explain what a given automation is for.
When It’s a Habit Problem, Not a Software Problem
A side spreadsheet or a stack of unexplained automations is usually evidence that habits slipped, not that Insightly stopped working. Swapping tools just carries the same undocumented mess into a new system.
If two or more of those ring true, book a cleanup before your next big push. A tidy base makes every other best practice on this list work as intended.
Insightly Best Practices FAQ
Disclaimer: This article shares general Insightly best practices drawn from our own project work and is offered for informational purposes only. Insightly’s features and plans can change over time, so verify the current details with Insightly before you act on anything here. SuvoCRM operates as an independent CRM agency with no ties to Insightly, and this piece is neither sponsored nor endorsed by them.