The importer is built for a load somebody starts by hand. When a billing system or an email platform has to agree with Insightly every week, the export, edit and re-import loop never ends, and one slipped column in an update import can't be taken back.
That's the part n-frames builds for Insightly accounts: an API job that updates contacts by Record ID as they change in the other system, or a one-time migration from an old CRM with dedupe rules and field mapping written for that data, so its mess doesn't land in Insightly.
Website forms don't need the importer at all. Insightly builds Web to Contact and Web to Lead forms under System Settings: you pick the fields, copy the generated HTML onto your site, and each submission becomes a tagged contact or lead, with lead assignment rules applied if you use them. Unbounce also connects directly. Insightly's form article doesn't describe a check against contacts you already have, so a returning customer can arrive as a fresh lead. Where that matters, n-frames builds the form handler on the Insightly API that matches each submission to an existing contact before creating anything new.