Descrição
O addon GravityImport – Import entries from a CSV importa registros em massa de arquivos CSV diretamente para formulários do Gravity Forms, com mapeamento de campos, regras condicionais para filtrar quais linhas entram e validação automática que bloqueia entradas inválidas. Dentro do ecossistema GravityKit, o componente suporta todos os tipos de campo do Gravity Forms, atualiza entradas existentes via coluna Entry ID e exporta as linhas com falha em CSV separado para revisão e reimportação.
Características Principais
- Mapeamento completo de campos
Cobre todos os tipos de campo do Gravity Forms, além dos metadados de entrada. - Atualização por Entry ID
Inclui uma coluna Entry ID no CSV para sobrescrever entradas existentes em vez de duplicar. - Regras condicionais de importação
Filtra quais linhas do CSV serão importadas com base em condições configuráveis. - Validação automática de dados
Bloqueia entradas incompletas ou inválidas durante o processo, mantendo a base limpa. - Exportação de linhas com falha
Gera um CSV apenas com os registros rejeitados para revisão e correção rápidas.
Benefícios do GravityImport – Import entries from a CSV
- Importação em alta escala
Processa CSVs com milhares de entradas sem travar o painel do WordPress. - Criação rápida de formulários
Gera um novo formulário automaticamente a partir do cabeçalho do próprio arquivo CSV enviado. - Compatibilidade com add-ons do Gravity Forms
Executa feeds de add-ons compatíveis durante a importação, mantendo automações ativas. - Suporte a arquivos enviados
Importa arquivos referenciados em campos do tipo File Upload do Gravity Forms.
Para Quem é Indicado?
- Equipes que precisam migrar entradas entre formulários do Gravity Forms ou consolidar bases de submissões.
- Agências e administradores que gerenciam grandes volumes de leads, inscrições ou pedidos em planilhas externas.
- Profissionais que trabalham com exports de outros sistemas e querem reaproveitar esses dados em formulários do WordPress.
Para quem opera Gravity Forms em escala, o componente elimina a fricção de povoar formulários sem submissão manual, conectando planilhas externas, exports de CRMs e backups de entradas a um único fluxo de importação no admin. A execução de feeds compatíveis durante o import mantém integrações de notificação, pagamento e marketing rodando normalmente, e o CSV de falhas devolve controle imediato sobre o que ficou de fora.
Perguntas Frequentes
O plugin GravityImport – Import entries from a CSV é GPL?
Sim. O GravityImport – Import entries from a CSV é distribuído sob a licença GPL (GNU General Public License). Você pode usar, modificar e redistribuir legalmente, em quantos sites quiser.
Posso usar o plugin GravityImport – Import entries from a CSV em mais de um site?
Sim. Você pode instalar o GravityImport – Import entries from a CSV em quantos sites quiser. Só as atualizações automáticas pelo Ultrapack Auto Updater têm limite: de 3 a 80 sites, conforme o plano.
Quanto custa o plugin GravityImport – Import entries from a CSV no Ultrapack?
O GravityImport – Import entries from a CSV sai por R$ 14,90 na compra avulsa, e também está incluído nos planos de assinatura a partir de R$59/mês (VIP I).
O plugin GravityImport – Import entries from a CSV inclui atualizações?
Sim. A versão atual do GravityImport – Import entries from a CSV é a 2.12.4, publicada no Ultrapack em 09/10/2026. Assinantes atualizam direto do painel do WordPress com o UAU (Ultrapack Auto Updater).
O plugin GravityImport – Import entries from a CSV é seguro para baixar e instalar no meu WordPress?
Sim. Cada versão do GravityImport – Import entries from a CSV passa por varredura de malware (ClamAV e regras YARA, no UltraHub) antes de ser publicada.
Quais são os requisitos do plugin GravityImport – Import entries from a CSV?
Requer WordPress 6.2 ou superior e PHP 7.4.0 ou superior. Testado até o WordPress 7.1.1.
O que mudou nesta versão
Versão 2.12.4
- This release fixes several import issues, including Dynamic Lookup fields that imported nothing and imports that never started.
- Columns mapped to a Dynamic Lookup field set to "Multiple Choice" with multiple selections allowed imported nothing even though the import reported success; cells listing the field's stored values, such as record IDs (`3, 1`), now select those choices.
- Entries imported in the background could have no "Created By" user, and imported notes without their own author had none either (both now belong to the user who started the import).
- Imports stayed on "Preparing to import…" and never ran when GravityKit's "Enable Background Processing" setting was off but GravityImport's was on (these imports now run in the browser).
- With Gravity Forms 3.0.3 or newer, rows rejected for the form as a whole, such as a row whose only value was in a field hidden by conditional logic, were blamed on an anti-spam or CAPTCHA plugin instead of showing Gravity Forms' reason.
- 🔧 Updated
- [Foundation]
Versão 2.12.3
- This update fixes Quiz scoring, File Upload, and choice field import issues, along with incorrect messages shown while mapping fields.
- Note: GravityImport now requires Gravity Forms 2.9.4 or newer.
- Imported Quiz entries could have the wrong score, percentage, and grade because the form's last question was skipped and the one before it was counted twice.
- File Upload field issues
- Files imported into a single-file File Upload field created with Gravity Forms 2.10 or newer did not appear on the entry, its Edit screen, in Views, or in merge tags, even though the files were downloaded
- When a row kept a file link formatted as a list
- After a row failed to import, later rows stored single-file File Upload values as a list instead of a single link.
- A CSV column mapped to the "(Any Choice)" option of a Checkboxes, Multiple Choice, or Image Choice field left every box unchecked when a cell listed several comma-separated choices (for example, `friday,saturday`).
- The "Email Will Be Rejected" notice on the Map Fields step showed "%s" instead of the email patterns Gravity Forms rejects.
- The format dialog for unrecognized dates and times named MM/DD/YYYY or hh:mm AM/PM as the default even when another format was in use, such as YYYY-MM-DD hh:mm:ss for Entry Date.
- 💻 Developer Updates
- Added `gk/gravityimport/column/checkbox/delimiter` filter to change the separator between choices in a cell mapped to "(Any Choice)" (comma by default).
- 🔧 Updated
- [Foundation]
Versão 2.12.2
- This release fixes issues with importing Consent fields.
- Note: GravityImport now requires WordPress 6.5 or newer.
- Issues when importing Consent fields
- The form's consent text could be overwritten, and imported entries linked to the wrong version of the terms
- Consent terms containing `%` or `_` were saved as a new version on every import.
- 🔧 Updated
- [Foundation]
Versão 2.12.1
- This release fixes importing into Multiple Choice and Image Choice fields, and into file upload fields on Gravity Forms 3.1.2 or newer.
- Files were not imported into file upload fields on Gravity Forms 3.1.2 or newer, which rejected every row with "The file is not valid."
- Multiple Choice and Image Choice fields set to "Select One" could not be mapped as a single column — the mapping step offered only their individual choices, and the column was dropped while the import still reported success.
- Existing mappings to an individual choice are now rejected with a message naming the field to map instead, or skipped with a warning when an import profile runs from the command line.
- Multiple Choice and Image Choice fields that allow more than one selection stored cell values such as `1`, `yes`, `0` or `no` as the selected choice instead of treating them as Checkbox columns do.
- `1`, `true` or `yes` selects the choice, while `0`, `false`, `no` or an empty cell leaves it unselected
- "(Any Choice)" is available as a mapping target
- Rows that don't meet an "Exact Number" or "Range" selection limit are reported as errors.
- Row errors showed HTML character codes such as `<` and `&` in the import log and the failed records download, including around formatted text in Gravity Forms messages.
- 🔧 Updated
- [Foundation]
Versão 2.12.0
- This release gives clearer reasons when rows fail to import, and fixes file upload imports on Gravity Forms 3.0+, a fatal multi-file upload field error, and compatibility issues with GravityView and WordPress 6.7.
- ✨ Improved
- Rows rejected by a form-level validation failure now report the actual cause instead of "Failed validation: Unknown" — including when Gravity Forms is blocking submissions while its database upgrade is pending (common on freshly cloned staging sites), or when an anti-spam or CAPTCHA plugin rejects the submission.
- Entries imported with an Entry Status column using different capitalization (e.g., `Active`) could not be opened or edited in [GravityView]( the standard statuses (`active`, `spam`, `trash`) are now saved in the lowercase form Gravity Forms expects.
- Resolved a "translation loading was triggered too early" notice on WordPress 6.7+.
- Imports with a file upload column failed on Gravity Forms 3.0+ — downloaded files are now given a temporary name matching the uploaded file's extension, which Gravity Forms 3.0+ requires.
- A row rejected by a multi-file upload field caused a fatal error on PHP 8; on PHP 7.4 the error named the field but left the reason blank.
- 🔧 Updated
- [Foundation]
Notas de versão publicadas pelo desenvolvedor.
Como instalar
Atualização automática: este item é atualizado pelo Ultrapack Auto Updater. Com ele instalado, a versão nova aparece no seu painel como qualquer outra atualização do WordPress (como configurar).
- Baixe o arquivo
gravityview-importer.zip. - No painel do WordPress, vá em Plugins > Adicionar novo > Enviar plugin.
- Selecione o arquivo
gravityview-importer.zipe clique em Instalar agora. - Clique em Ativar.
Requisitos: Requer WordPress 6.2 ou superior e PHP 7.4.0 ou superior. Testado até o WordPress 7.1.1.
Travou em algum passo? Abra um chamado dizendo em qual deles parou.

UAU Ready