Migrate your Knack data

Tables are the core container for all Knack data. Every app has at least one table; some have dozens. We map each Table to the nearest CRM object (e.g., Contacts, Companies) and preserve the table schema including field order and display labels.

Knack supports 15+ field types (text, number, currency, date, connection, file, equation, etc.). Custom fields are common. We inspect the full field inventory per table, map standard types 1:1, and flag formula/equation fields that may need recalculation in the destination.

Individual rows in a Table. We export all records via the Object API, respecting pagination. Large tables are chunked to avoid timeout. Record IDs are exported as string identifiers; we map them to destination primary keys.

Connection fields link one Table to another (one-to-many or many-to-many). These are Knack-specific foreign keys. We translate them into relationship fields on the destination CRM object using the linked record IDs as reference.

Views are saved filtered or sorted subsets of a Table. They are a Knack UI concept rather than a CRM-native object. We document which Views exist and replicate their filter logic as saved views or custom queries on the destination object.

Pages are the UI layer exposing Views to end users. Knack organizes Pages into Groups. We export Page structure as a sitemap reference; the destination will not replicate the exact UI but the underlying data will be organized identically.

File fields store documents, images, and PDFs. Files are accessible via direct URLs after authentication. We download and re-upload each file to the destination CRM, preserving the attachment relationship to the parent record.

Knack roles control which Pages and Records users can access. We export role names and permissions as metadata. The destination CRM may use Profiles, Roles, or Teams; we map permissions to the closest equivalent.

Workflow rules (email notifications, field updates, record creation triggers) exist within Knack and have no direct equivalent in standard CRMs. We document workflow configurations in a separate sheet but do not migrate them, as they require rebuilding on the destination platform.

Available on Pro and above. Scheduled tasks run background jobs at defined intervals. We flag their existence and document the schedule; rebuilding them on the destination is out of scope for data migration but is noted as a post-migration task.

CSS/JS customizations, logo settings, and theme choices are purely cosmetic. We do not carry them forward. Email templates using Knack's custom domain settings are documented and referenced separately.

Record History tracks changes to field values. It is available on Pro (1 month) and Corporate (2 months) plans. We export available history records as an Audit Log object on the destination, if supported.

SSO settings (Basic on Starter, Advanced on Pro/Corporate) are plan-gated. We document the SSO method and map it to the destination identity provider configuration. This is a post-migration configuration step, not data migration.

Healthcare deployments on Knack Health involve PHI and require a signed BAA. We handle PHI migration under additional security controls and flag any encrypted or restricted fields that require special handling before the BAA is transferred.