Migrate from Cirqll to Nutshell

Discovery and Cirqll API schema probing

We audit the Cirqll account to identify all record types (Customers, Leads, Tasks, Activities, Notes, Calendar Events, Documents) and approximate volumes. Because Cirqll's full API schema is not publicly documented, we run a controlled probe-read phase using the documented Customer endpoint and additional endpoints discovered during exploration, constrained to the 100 req/min rate limit. We map the discovered field names, types, required flags, and relationships before designing the Nutshell target schema. We also request confirmation of the customer's Cirqll plan tier to verify API access availability.

Nutshell target schema design

We design the Nutshell destination schema based on the discovered Cirqll field map. This includes provisioning custom fields on Person, Company, and Lead using Nutshell's custom fields API (available on all paid tiers). We design the Lead status mapping if Cirqll status values differ from Nutshell's default. We identify pipeline configuration needs (Nutshell supports up to 5 pipelines on Pro) and configure Record Types if the customer's Cirqll data uses multiple deal or lead categories. Schema is validated against a test Nutshell account before production migration begins.

Owner reconciliation and User provisioning

We extract every distinct Cirqll User referenced on Leads, Tasks, and Activity records and match by email against the Nutshell destination account's User list. Any Cirqll owner without a matching Nutshell User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Nutshell's User provisioning is handled by the customer's admin in Settings; we provide the list of required users with their email and role.

Staged production migration with rate-limit pacing

We run production migration in record-dependency order with staggered batches to respect the 100 req/min Cirqll rate limit. Phase 1: People (from Cirqll Customers). Phase 2: Leads with the status mapping applied. Phase 3: Companies (if separate from Person records). Phase 4: Tasks and Activities with owner resolution and Person/Lead lookup linking. Phase 5: Notes relinked to Person or Lead. Phase 6: Calendar Events as Activity records. Each phase emits a row-count reconciliation report before the next phase begins. We monitor for HTTP 429 responses and apply dynamic backoff.

Document migration secondary pass

We provide a document inventory list identifying every Cirqll document, its parent record (Person, Lead, Company), filename, and upload date. The customer exports these manually from the Cirqll UI, and we reattach them to the corresponding Nutshell record using Nutshell's file attachment API. Original filenames and upload timestamps preserve; version history does not transfer. This phase runs as a separate engagement or as an add-on scope after the structured record migration is complete.

Cutover, validation, and handoff

We freeze Cirqll writes during the cutover window and run a final delta migration of any records modified during the migration period. We validate a random sample of migrated records against the Cirqll source data and deliver a reconciliation report with record counts per object and any unmapped fields or rejected records. We do not rebuild workflows because Cirqll has no visible workflow engine; if Nutshell automation is needed, we provide a written guide on setting up Nutshell's built-in workflow triggers. Post-migration support covers a one-week window for reconciliation issues.