Migrate from iPlan to Jira

iPlan Projects export with status, dates, budget, owner, and description. We map directly to Jira Projects with the project key derived from the iPlan project code or name prefix. Project-level custom fields migrate as Jira custom fields pre-created in the destination project before data load. The Jira project type (team-managed or company-managed) is selected during scoping based on the customer's governance model.

iPlan Tasks map to Jira Issues with the mapping between iPlan Task type and Jira Issue type defined during scoping (standard tasks typically become Jira Stories or Tasks). Core fields (name, description, start/end dates, status, priority) migrate directly. Assigned resources resolve to Jira User accounts by email match. Subtasks nested under Tasks map according to the Jira project type: company-managed projects support Sub-Task Issues; team-managed projects use linked Issues or Labels for hierarchy.

iPlan Milestones export with target dates and parent Project association. We reconstruct milestones in Jira as Fix Versions (Releases) attached to the corresponding project. Milestone interdependencies do not map directly; Jira's Advanced Roadmaps (Premium tier) supports cross-project dependencies between Issues, but milestone-level interdependency tracking is documented as a gap for your admin to address through Jira Automation rules or Advanced Roadmaps configuration.

iPlan Subtasks nested under Tasks require schema decision during scoping. In company-managed Jira projects, Subtasks map to Jira Sub-Task Issue type with parent Issue linking preserved. In team-managed projects (which do not support Sub-Task Issue type), we flatten subtasks into linked Issues and set the parent reference as a custom field or Link type so the hierarchy remains navigable. The customer's Jira project type choice drives the final mapping approach.

iPlan Resources (employee records) export with name, email, role, and availability schedule. We resolve Resources to Jira User accounts by email match. Resources without a matching Jira User are held in a reconciliation queue for your admin to provision. Availability schedules and capacity data do not map to Jira natively; if capacity planning is required, we recommend Tempo Timesheets (Atlassian Marketplace) as the post-migration replacement for iPlan's resource scheduling.

iPlan Timesheet records (hours logged, date, project association, task linkage) migrate to Jira worklog entries if Jira Software Premium with time tracking enabled is the destination. If the Jira destination does not have time tracking enabled, we import timesheet data as Issue History comments with a standardized format (date, hours, task reference) so the data is preserved even if Jira-native worklog is not in scope. Any timesheet entries with orphaned project references are flagged for manual reconciliation.

iPlan custom fields on Projects, Tasks, and Milestones require explicit field-type mapping before migration. Dropdown, numeric, and text fields map with minimal transformation to equivalent Jira custom field types. Formula fields and rollup calculations in iPlan do not have Jira equivalents and are documented as fields requiring rebuild in Jira using Calculated Fields (Marketplace) or manual computation post-migration. Custom fields are pre-created in Jira before any data import.

iPlan workflow rules encode business logic in a proprietary format that cannot export directly. We extract every active iPlan workflow rule as a human-readable specification (trigger, conditions, actions) during scoping and deliver a written workflow inventory with recommended Jira Automation equivalents. The customer's admin rebuilds automations in Jira Automation for Jira (included at Standard and Premium tiers) post-migration. We do not migrate workflow rules as executable code.

iPlan Knowledge Base articles export as structured content but lack consistent tagging taxonomy. We extract article text, attached files, and category assignments. For organizations already using Confluence, we recommend migrating articles to a Confluence Space with preserved category structure. For Jira-only destinations, articles migrate as Jira Issues (labeled as Knowledge Article) with the text in the description field and attachments preserved.

iPlan Billing and financial tracking records do not have a direct Jira equivalent. Jira does not support native billing or invoicing. We extract billing data as structured CSV exports alongside the Jira migration, flagging invoice numbers, amounts, project associations, and payment status. Customers with ongoing billing requirements configure integration with an external accounting tool or CRM with billing support.

File attachments associated with iPlan Projects, Tasks, or Knowledge articles are extracted and uploaded to the corresponding Jira project Issues. File names and upload timestamps are preserved. Jira has a per-attachment file size limit (10 MB on Free and Standard, 50 MB on Premium and Enterprise); files exceeding these limits are flagged before migration so the customer can decide whether to compress, split, or store externally. Attachments with null filenames in iPlan cannot migrate and are documented in the extraction report.

iPlan report configurations and dashboards use proprietary visualization schemas that cannot migrate to Jira. We export the underlying data (project metrics, task completion rates, earned-value figures) as structured CSV during scoping so reports can be rebuilt in Jira's native reporting (for team-managed projects) or in a third-party reporting tool. Jira Software Premium includes Advanced Roadmaps for cross-project reporting.