Migrate from Knack to Pipedrive

Knack Tables containing customer contact fields (name, email, phone, address) map to Pipedrive Person. We inspect field types to identify the primary contact table: text fields named 'name', 'email', 'phone' map to Pipedrive Name, Email, and Phone fields. Multiple person-facing Tables in one Knack app may indicate multiple record types; we consolidate into a single Person object with a type custom field if the customer confirms the Tables represent one logical entity.

Knack Tables storing company or business entity records map to Pipedrive Organization. Fields named 'company', 'business', 'organization' map to the Organization Name field. Address fields map to Pipedrive's address compound field. If the Knack app lacks a separate organization Table and contact records store company name as a text field, we create Organization records from the distinct company name values and link the Person records via Organization ID lookup.

Knack Tables tracking revenue transactions, sales opportunities, or project-based work map to Pipedrive Deal. Fields representing monetary value map to Pipedrive's value field, and stage-like fields (text or dropdown) map to a Deal Stage in the customer's pipeline. We configure the Pipedrive pipeline and stages before migration so that stage values import into the correct dropdown rather than creating orphaned text values.

Knack Connection fields define relational links between Tables (e.g., a Tasks Table linked to a Contacts Table). We resolve these as Pipedrive links: a one-to-many from Organization to Person becomes an Organization-Person link; a one-to-many from Deal to Person becomes a Deal-Person link. We export the Knack record ID alongside the connected record's identifier so that link resolution happens at migration time rather than in a post-processing step.

Knack many-to-many relationships use a junction Table between two parent Tables. We decompose these into a mapping approach: if the junction holds meaningful data beyond the link (dates, notes, role names), we create a custom Activity or Note record in Pipedrive to carry that context. If the junction is a pure link table, we use Pipedrive's Activity linking or a documented reference sheet rather than creating a custom object.

Knack File fields store documents, images, and PDFs accessible via authenticated URLs. We download each file from Knack and re-upload to Pipedrive attached to the relevant Person, Organization, or Deal record. Files exceeding 25 MB are flagged for the customer to store externally with a link embedded in a Pipedrive Note, since Pipedrive's attachment limits are 25 MB per file.

Knack Record History tracks field-level changes on Pro (1 month) and Corporate (2 months) plans. We export available history records as Note entries with a timestamp and the change description. If the customer needs a full audit trail, we document the export format for import into a compliance tool or a custom Pipedrive analytics object.

Knack roles control Page and Record-level access. We export role names and permission structures as metadata. Pipedrive maps permissions to User-level access (full, limited, or restricted) and Team membership. We create the Team structure in Pipedrive and document the mapping from Knack roles to Pipedrive access levels for the admin to configure post-migration.

Knack Views are saved filtered or sorted subsets of a Table with no direct Pipedrive object equivalent. We export every View's name, filter logic, sort order, and visible columns. In Pipedrive, we create saved filters that reproduce the record subset logic. The admin applies these to the migrated data post-import. This is a documentation deliverable, not an automated import step.

Knack automation rules (email notifications, field updates, record triggers) do not migrate. They are structurally different from Pipedrive's automation builder (which uses triggers, conditions, and actions in a visual editor) and there is no automated conversion path. We deliver a written inventory of every active Knack Workflow with its trigger type, conditions, and actions, plus a recommended Pipedrive Automation equivalent and a rebuild checklist for the customer's admin.