Add link to readme: Meistertask migration tool

Open Beginner friendly
#8,654 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
90/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Domain
documentation

Research direction

Read the 3rd-party integrations section of README.md, linked in the issue. Add the provided meister2nc entry there; the work is done when the README links to the migration tool and describes what it migrates.

Written by the indexing model from the issue text.

Description

I migrated users in my workplace from Meistertask to Deck. I used their MCP connector to migrate meistertask to Deck and meisternotes to Collectives.
I just published the codebase for that, feel free to add this in your readme section:

  • meister2nc - Migrates MeisterTask projects (cards, comments with authors, attachments, labels, ACLs, dependencies) to Deck

In any case, feel free to close this issue right away.

The migration tool has achieved 99% of what could have been possible, for the size of our userbase that was enough.
(Lacking 1%: User mentions inside card descriptions, group structures in meister that we never used)

Dominant language
JavaScript
Stars
1.4k
Forks
363
Avg merge
1d 5h
Merged PRs (30d)
116

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nextcloud/deck

All issues in nextcloud/deck

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.